CN110603874A

CN110603874A - New radio control channel resource set design

Info

Publication number: CN110603874A
Application number: CN201880027626.8A
Authority: CN
Inventors: 郭勇俊; 苗洪雷; 德布迪普·查特吉; 熊岗; 何宏; 李大远
Original assignee: Intel IP Corp
Current assignee: Apple Inc; Intel Corp
Priority date: 2017-05-05
Filing date: 2018-05-04
Publication date: 2019-12-20
Anticipated expiration: 2038-05-04
Also published as: CN116961833A; EP3620006A4; US20190357185A1; US11659564B2; EP3620006A1; WO2018204806A1; CN110603874B

Abstract

Embodiments herein may involve sending an indication of a first set of parameters related to a control channel in a first physical channel transmission; and transmitting an indication of a second set of parameters related to the control channel in the control channel transmission using the first set of parameters. Further embodiments may involve identifying a first parameter related to REGB for interleaved PDCCH transmissions, wherein the first parameter is selected from a first plurality of parameters; interleaving the REGB based on a first parameter to form a CCE; and the CCE is transmitted in a PDCCH transmission. Other embodiments may be described and/or claimed.

Description

New radio control channel resource set design

Cross Reference to Related Applications

This application claims the benefit of U.S. provisional application No. 62/501,883 filed on 5/2017 and also claims the benefit of U.S. provisional application No. 62/567,158 filed on 10/2/2017, each of which is incorporated herein by reference in its entirety.

Technical Field

Embodiments of the present disclosure relate generally to the field of cellular communications, and more particularly to control information in such communications.

Background

Mobile communications have evolved greatly from early voice systems to today's highly sophisticated integrated communication platforms. Next generation wireless communication systems, which may be referred to as fifth generation (5G), New Radio (NR), or some other terminology, may provide access to information and sharing of data anywhere, anytime, by various users and applications. NR is expected to be a unified network/system that may satisfy vastly different and sometimes conflicting performance dimensions and service requests. This diverse multidimensional requirement can be driven by different services and applications. In general, NR may be similar to or derived from aspects of third generation partnership project (3 GPP) long term evolution-advanced (LTE-a) technology, with additional potential new Radio Access Technologies (RATs) to enrich people's lives with better simple and seamless wireless connectivity solutions.

In some NR networks, one or more sets of control channel resources (which may be referred to as CORESET) may be configured by the network and sent to a User Equipment (UE). To support transmission of common channels, e.g., transmission of system information on common channels, a common CORESET may be configured for the UE. Further, it is also possible that UE-specific CORESET may be configured for transmission of the UE-specific data channel.

In some other NR networks, an interleaver may be used to implement distributed transmission of a NR physical downlink control channel (NR-PDCCH). Each NR-PDCCH transmission may consist of one or more Control Channel Elements (CCEs). Each CCE may consist of six Resource Element Groups (REGs), each of which may include 12 contiguous subcarriers. To achieve better channel estimation performance, several adjacent REGs in time or frequency may form a REG bundle (REG bundle, REGB). For example, a REGB may comprise several adjacent REGs, e.g. 2, 3 or 6 REGs, all of which are applied with the same precoding. As a result, a CCE may include one or more REGBs. The number of REGBs in a CCE may depend, for example, on the size of the REGBs. Depending on the size of the CORESET, the CORESET may consist of multiple one or more REGs, REGBs, or CCEs. The time-first or frequency-first numbered REGBs in CORESET may be fed sequentially into the interleaver, and the sequential REGBs at the output of the interleaver may be used to construct CCEs with consecutive logical indices. These CCEs may form NR-PDCCH core transmissions as described above.

Drawings

Fig. 1 illustrates an example CCE distribution over CORESET using an interleaver according to various embodiments.

Fig. 2 illustrates an alternative example CCE distribution over CORESET using an interleaver according to various embodiments.

Fig. 3 illustrates an alternative example CCE distribution over CORESET using an interleaver according to various embodiments.

Fig. 4 illustrates an example technique for generating interleaved PDCCH transmissions, in accordance with various embodiments.

Fig. 5 illustrates an example initial access technique, in accordance with various embodiments.

Fig. 6 illustrates an example CORESET transmission in an NR slot in accordance with various embodiments.

Fig. 7 illustrates an example technique for transmitting control parameters, in accordance with various embodiments.

Fig. 8 illustrates an alternative example technique for generating interleaved PDCCH transmissions, in accordance with various embodiments.

Fig. 9 illustrates an example architecture of a system of networks, in accordance with various embodiments.

Fig. 10 illustrates an alternative example architecture of a system of networks, in accordance with various embodiments.

Fig. 11 illustrates an example of an infrastructure device, in accordance with various embodiments.

FIG. 12 illustrates an example of a computer platform, in accordance with various embodiments.

Fig. 13 illustrates example components of a baseband circuit and Radio Front End Module (RFEM), in accordance with various embodiments.

Fig. 14 illustrates example interfaces of a baseband circuit, in accordance with various embodiments.

Fig. 15 is an illustration of a control plane protocol stack in accordance with various embodiments.

Fig. 16 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the techniques, processes, or methods discussed herein, according to some example embodiments.

Detailed Description

In the following detailed description, reference is made to the accompanying drawings which form a part hereof wherein like numerals designate like parts throughout, and in which is shown by way of illustration embodiments in which the subject matter of the present disclosure may be practiced. It is to be understood that other embodiments may be utilized and structural or logical changes may be made without departing from the scope of the present disclosure. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the embodiments is defined by the appended claims and their equivalents.

For the purposes of this disclosure, the phrase "a or B" means (a), (B), or (a and B). For the purposes of this disclosure, the phrase "A, B or C" means (a), (B), (C), (a and B), (a and C), (B and C), or (A, B and C).

The description may use the phrases "in an embodiment" or "in embodiments," which may each refer to one or more of the same or different embodiments. Furthermore, the terms "comprising," "including," "having," and the like, as used in connection with embodiments of the present disclosure, are synonymous.

The term "coupled with …" and derivatives thereof may be used herein. "coupled" may mean one or more of the following. "coupled" may mean that two or more elements are in direct physical or electrical contact. However, "coupled" may also mean that two or more elements are in indirect contact with each other, but yet still co-operate or interact with each other, and 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.

Various operations may be described as multiple discrete operations in turn, in a manner that is most helpful in understanding the claimed subject matter. However, the order of description should not be construed as to imply that these operations are necessarily order dependent.

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

Embodiments herein may be described with reference to various figures. Unless explicitly stated otherwise, the dimensions of the figures are intended to be simplified illustrative examples rather than depictions of relative dimensions. For example, the various lengths/widths/heights of elements in the figures may not be drawn to scale unless otherwise indicated.

CORESET configuration

As described above, the REGB of time-first or frequency-first numbers in CORESET may be sequentially fed into the interleaver, and the sequential REGB at the output of the interleaver may be used to construct CCEs with consecutive logical indices. The NR-PDCCH may then be constructed from CCEs. A number of different interleaving schemes may be used.

In a first scheme, referred to herein as option Alt-1, a Long Term Evolution (LTE) PDCCH or enhanced PDCCH interleaver operating on one or more REGBs may be used. The interleaver may comprise two steps, namely a block interleaver followed by column permutation. The input data may be written row by row into the interleaving matrix in column ascending order, followed by column permutation of the interleaving matrix. The data may then be read out of the interleaving matrix column by column in ascending row order.

In a second scheme (referred to herein as option Alt-2), a one-step block interleaver may be used. In contrast to Alt-1, column permutation may not be applied. Some variations of Alt-2 may depend on how the number of rows in the interleaving matrix is selected. For example, in some embodiments, the number of rows may be configurable, while in other embodiments, the number of rows may depend on the REGB size.

In a third scenario (referred to herein as option Alt-3), two phases may be used. In the first step, interleaving may be within X REGBs, where the interleaving unit is REGB. The second interleaving may be within CORESET, where the unit of interleaving is Y Resource Blocks (RBs). Similarly, depending on how the interleaving matrix is written or read, some variations of Alt-3 may be possible, for example written or read in a pseudo-random manner or in a conventional manner as in block interleaving in Alt-1 or Alt-2.

Design goals for the interleaver may include achieved frequency diversity, randomization of CCEs as the output of the interleaver, and potential positive impact on blocking probability caused by multiple overlapping CORESET configurations. However, the options Alt-1, Alt-2 or Alt-3 may be both pros and cons. Thus, different interleaving options may be preferred due to tradeoffs in design goals involved.

Some embodiments herein may involve a fully configurable interleaving approach such that all different options may be implemented by a particular parameterized configuration. As a result, the network may select a preferred interleaving scheme based on the desired design goals and system control resource configuration.

Embodiments herein may relate to a configurable interleaver. The interleaver may be suitable for NR-PDCCH transmission, for example, and is particularly suitable for distributed NR-PDCCH transmission. The interleaver may include several configurable parameters. One such parameter may be the number of interleaver stages. For example, the interleaver may have one or more stages.

Another parameter may include an interleaving unit in terms of the number of REGBs for one of the one or more stages. That is, for this stage, whether the interleaver operates on a single REGB or multiple REGBs. Other parameters may include the number of rows or the number of columns in the interleaving matrix of the interleaver for one of the one or more stages. Another parameter may include a column permute pattern vector for a stage of the one or more stages. The column permutation pattern vector may be a function of a Cell Identifier (CID), a Virtual Cell Identifier (VCID), a UE identifier (UE ID), or some other parameter.

These configurable settings may enable the interleaver to achieve a desired tradeoff between: frequency diversity, randomization of allocated CCEs, and potential congestion mitigation between multiple overlapping CORESET configurations. In some embodiments, some of the configurable parameters may be a function of other parameters, such that the set of freely configurable parameters may be reduced. More specifically, the proposed configurable interleaver may incorporate various of the above-described alternative options (Alt-1, Alt-2, Alt-3) into a unified framework, such that the network may select a particular interleaving method depending on the exact context of the network configuration. This may allow the network to achieve a compromise between the relevant performance goals. In other words, the network may be able to configure the interleaver based on certain desired goals and purposes, and adjust the interleaver as these goals/purposes change.

Fig. 1-3 depict various examples of CCE distributions over CORESET using an interleaver according to various embodiments. In these embodiments, the configurable interleaver may include one or several sequential interleaving stages. The number of interleaving stages N _ I may be configurable. The configurable interleaving stage may involve three stages. Specifically, in stage 1, the configurable rectangular interleaving matrix may be populated row by row in column ascending order. In stage 2, a configurable column permutation operation is performed on the padded interleaving matrix. In phase 3, the interleaving matrix is read column by column in ascending row order.

The following parameters may be configured in the nth interleaving stage, where N1.. N _ I:

1. interleaving unit in terms of number of REGBs: b _ n

2. Number of rows of the interleaving matrix: r _ n

3. Number of columns of the interleaving matrix: c _ n

4. Column permutation function: c _ p ═ f _ n (C), where C ═ 1, 2.

In some embodiments, not all of the above parameters may be used. For example, in some embodiments, the column permutation function c _ p may not be used, or other parameters may not be used. With the configurable interleaver and parameters described above, different interleaver configurations can be implemented. In the embodiments described below, let X denote the number of REGBs in CORESET. Let Y denote the number of REGBs per CCE.

Fig. 1 illustrates an example CCE distribution over CORESET using an interleaver according to various embodiments. Specifically, in fig. 1, N _ I is 1. B is 1. And R is Y. C is X/Y. f _1 may be some deterministic function of CID, VCID, UE ID, or some other parameter. Specifically, in fig. 1, X may be equal to 16 and Y may be equal to 2. In general, FIG. 1 may depict an interleaving technique that uses a configurable interleaver to perform Alt-1 as described above.

Fig. 1 depicts 16 REGB indices, numbered 1-16, at 100. These indices may be organized into a 2x 8 interleaving matrix at 105. In particular, it can be seen that the REGB can be written row by row in column ascending order into the interleaving matrix at 105. Column permutation on the interleaving matrix may be performed at 110. Specifically, c _ p may be equal to [1,5,3,7,2,6,4,8], where each entry defines a column index prior to a column permutation. In this example, column 2 of the matrix after permutation should be column 5 of the matrix before permutation. The CCE index corresponding to the column index of the column permuted matrix is depicted at 115. For example, the 5 th CCE, i.e., the 5 th column of the matrix which is a shaded column in 110 and 115, is constituted by REGB #2 and # 10. As a result, the 5 th CCE allocation is shown at 120, where each index in each block represents a CCE index and the numbers below each block represent the REGB index as in 100.

As can be seen from fig. 1, each CCE may be fully distributed over CORESET. In addition, CCEs with consecutive indices may be evenly distributed over CORESET, simplifying the construction of high aggregation level NR-PDCCH transmissions that include several consecutive CCEs in a hierarchical search space.

Fig. 2 illustrates an example CCE distribution over CORESET using an interleaver according to various embodiments. Specifically, in fig. 2, N _ I is 1. B is 1. R may be some preferred value (e.g., 4 as shown in fig. 2). And C is X/R. f _1 may be some deterministic function of CID, VCID, UE ID, or some other parameter. Specifically, in fig. 2, X may be equal to 16 and Y may be equal to 2. In general, FIG. 2 may depict an interleaving technique that uses a configurable interleaver to perform Alt-2 as described above.

Similar to fig. 1, a REGB index is depicted at 200. A 4x 4 interleaving matrix is depicted at 205. The column permutation c _ p may be equal to [1,3,2,4] and is depicted at 210. CCE indices are depicted at 215. CCE distributions in CORESET are depicted at 220.

As can be seen from fig. 2, the span of each CCE obtained from Alt-2 may be only in half of the CORESET, and two CCEs with consecutive indices may be distributed throughout the CORESET. If it is desired for the CCE to be located in half of the CORESET for reduced frequency distribution, the configuration of Alt-2 (and fig. 2) may contribute to this result.

Fig. 3 illustrates example CCE distributions over CORESET using an interleaver according to various embodiments. Specifically, in fig. 3, N _ I is 1. B is 1. R is 1. And C is X/2. The column permutation c _ p may not be used in this particular example. Specifically, in fig. 3, X may be equal to 16 and Y may be equal to 3. In general, FIG. 3 may depict an interleaving technique that uses a configurable interleaver to perform Alt-3 as described above.

Similar to fig. 1, a REGB index is depicted at 300. A 2x 6 interleaving matrix is depicted at 305. CCE indices are depicted at 315. CCE distributions in CORESET are depicted at 320.

As can be seen from fig. 3, when the number of rows in the interleaving matrix is smaller than the number of REGBs per CCE (i.e. Y), the resulting CCEs may be less distributed over CORESET, in particular it may span several segments of consecutive REGBs. However, such reduced-distribution CCE allocation may reduce the blocking probability of multiple overlapping CORESET configurations.

It will be understood that the embodiments described with reference to fig. 1-3 are intended as examples, and other embodiments may use one or more different parameters. For example, in other embodiments, the interleaving matrix may be of different sizes, the number of stages may be different, the column permutation may be different, the number of REGBs or CCEs may be different, and so on.

Fig. 4 illustrates an example technique for generating interleaved PDCCH transmissions, in accordance with various embodiments, such as those described above with reference to fig. 1-3. The technique can include identifying, at 405, a first parameter related to REGB for an interleaved PDCCH transmission. The parameter may be selected from the first plurality of parameters and may include, for example, the number of stages of the interleaver, the interleaving unit in terms of the number of REGBs (for a given stage), the number of rows or columns of the interleaving matrix used by the interleaver or stages of the interleaver, a column permutation pattern, some other parameter, or some combination of the above.

The technique may also include interleaving the REGB based on the identified first parameter to form a CCE, at 410. Examples of the interleaving may be as described above with reference to fig. 1-3. The CCE may then be transmitted in a PDCCH transmission at 415. Specifically, the CCE may be transmitted in NR-PDCCH transmission. In some embodiments, the CCE may be transmitted as part of the CORESET. It will be understood that in some embodiments, multiple CCEs may be formed at 410 and multiple CCEs may be transmitted at 415.

CORESET Transmission

As described above, in some embodiments, for system information delivery, the common CORESET configuration may be used by the UE to correctly receive system information. Further embodiments herein may relate to mechanisms to configure a common CORESET for receipt of system information.

In particular, as noted above, in some embodiments it may be desirable to configure a common CORESET for UEs for delivery of NR system information. In an embodiment, NR system information may be sent to NR UEs using three different channels. For example, in some embodiments, an NR physical broadcast channel (NR-PBCH) may transmit basic minimum system information (EMSI). Then, the NR-PDCCH or NR physical downlink shared channel (NR-PDSCH) may transmit Remaining Minimum System Information (RMSI). Other system information (oSI) may also be transmitted by the NR-PDCCH or the NR-PDSCH.

Fig. 5 illustrates an example initial access technique, in accordance with various embodiments. When the UE starts initial access, it may first perform initial synchronization by detecting a synchronization signal at 505. Such signals may be transmitted, for example, by a base station, an evolved node B (eNB), a Radio Access Network (RAN) node, or some other transmitter. For ease of reference, such transmitters may be referred to herein as "base stations" without loss of generality.

The UE may then receive the NR-PBCH transmission at 510. The NR-PBCH transmission may include, for example, EMSI as described above. The NR-PBCH transmission may be sent by the same base station as the synchronization at 505 or may be sent by a different base station.

The UE may then receive, at 515, random access procedure configuration information from the RMSI received in the NR-PDCCH or NR-PDSCH transmission. For the random access procedure, a random access response may be transmitted using the NR-PDCCH and the scheduled NR-PDSCH within the common CORESET so that the common CORESET may be configured. Once the common CORESET is configured, the UE may perform a random access procedure at 520. The random access procedure may include, for example, one or more of the following: the UE transmits a random access preamble on a Random Access Channel (RACH); a base station sends a Random Access Response (RAR) to UE; UE sends Msg3 transmissions, such as Radio Resource Control (RRC) connection requests or UE identity messages; and the base station sends an Msg4 transmission, such as a contention resolution message, to the UE. In other embodiments, the random access procedure may include one or more additional transmissions or messages.

In some embodiments, the random access procedure may include a transmission of oSI. For example, oSI may be sent by a base station as part of a RAR or Msg4 transmission. In some embodiments oSI may be transmitted by the base station using a common search space in a common CORESET or a UE-specific search space in a common CORESET. If oSI is sent in an on-demand manner, it may also be sent by the base station using the UE-specific search space in the UE-specific CORESET.

After the UE performs the random access procedure at 520, the UE may then receive the NR-PDSCH transmission of the NR-PDCCH transmission at 525 to receive other System Information Blocks (SIBs), thereby ending the initial access procedure.

In some embodiments, the random access procedure at 520 may not be used only for initial access as described in fig. 5. In other embodiments, the random access procedure at 520 may be used by the UE for other purposes, such as uplink synchronization, handover, beam-to-link establishment, and so on. Depending on the purpose of the random access procedure, the UE behavior may be changed. For example, only RACH preamble transmission and RAR may be needed for uplink synchronization.

For reception of RMSI and oSI, it may be desirable for the UE to first receive the NR-PDCCH transmission and then may schedule the NR-PDSCH transmission for delivery of RMSI and oSI. Thus, the UE may be expected to know the common CORESET parameter for reception of the NR-PDCCH or NR-PDSCH transmission, and the common CORESET parameter may be included with the NR-PBCH message at 510. However, the NR-PBCH may be a broadcast channel that may be received by a plurality of UEs. Therefore, it is necessary to transmit the NR-PBCH with high power and low code rate. Thus, in some embodiments, it may not be desirable to include too many information bits into the NR-PBCH. Since the configuration of common CORESET may require many information bits, it may be challenging to include all common CORESET parameters into the NR-PBCH transmission.

In one embodiment, a two-step CORESET configuration may be used. In particular, in some embodiments, to receive the RMSI, the UE may be required to monitor the NR-PDCCH and receive a corresponding NR-PDCCH transmission. Thus, for reception of a NR-PDCCH transmission, it may be desirable for the NR-PBCH transmission to indicate which downlink resources the UE should monitor for the NR-PDCCH transmission. To reduce the configuration information included in the NR-PBCH, in some embodiments, a subset of the CORESET information, i.e., information that may be considered "basic configuration information" for CORESET, may be included in the NR-PBCH transmission. The remaining CORESET configuration information may be included in the RMSI itself.

In general, CORESET may include a variety of parameters, including:

-a starting position in a frequency band or a Synchronization Signal (SS) block or a frequency gap or frequency offset between the NR-PBCH and a common CORESET. In some designs, the frequency offset may be equal to zero, no indication is required;

-Physical Resource Block (PRB) in CORESET (granularity may be CCE size) or number of CCEs;

-the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols in the CORESET;

-frequency-first mapping or time-first mapping for REG to CCE mapping;

-a frequency-first mapping or a time-first mapping for CCE to NR-PDCCH candidate mapping;

-whether CORESET is distributed or localized;

-REGB size in frequency domain. Alternatively or additionally, one default REGB size may be fixed and applied for NR-PDCCH transmission in common CORESET. The value may also be determined based at least on a configured resource size in terms of CCEs or Resource Blocks (RBs).

-a transmission scheme for CORESET;

-number of demodulation reference signal (DMRS) ports for transmitting CORESET;

-a group common NR-PDCCH configuration;

-slot offset and period of basic CORESET information;

slot duration (e.g., 7 or 14 symbols);

-parameter set (numerology) scheduling NR-PDCCH transmission of RMSI. Alternatively or additionally, the set of parameters for NR-PDCCH and RMSI scheduled by NR-PDCCH may be assumed to be the same as for NR-PBCH and may therefore not be explicitly signaled.

-quasi co-location (QCL) indication;

for QCL, an indication of the antenna port or channel, e.g. Primary Synchronization Signal (PSS)/Secondary Synchronization Signal (SSS), is quasi co-located with CORESET with respect to parameters such as doppler shift, doppler spread, average delay, delay spread, etc.

Further, some parameters related to the monitored search space for NR-PDCCH transmission (which may include scheduling RMSI) may include an indication of an aggregation level and an indication of a number of aggregation levels for NR-PDCCH monitoring. These parameters may be predetermined or may be indicated in the NR-PBCH transmission.

Note that in some embodiments, the frequency gap between a Synchronization Signal (SS) block and the basic CORESET may be defined in terms of a subcarrier spacing for transmission of the SS block, a predetermined subcarrier spacing, or a subcarrier spacing of a transmission configuration that schedules RMSI for NR-PDCCH.

Similarly, the slot offset and period of the basic CORESET may be defined according to the slot duration indicated in the NR-PBCH, a parameter set for transmission of SS blocks, or a predetermined parameter set.

Among the above parameters, only a subset of the parameters may be included in the NR-PBCH, which may be referred to as "basic" CORESET parameters, and the remaining parameters may be included in the RMSI. The basic CORESET configuration parameters may be parameters that are considered necessary for the UE to identify a subsequent CORESET transmission. The basic CORESET configuration parameters may include CORESET size or CORESET position in the frequency domain. Slot duration and other information may also be included in the NR-PBCH transmission in some embodiments. However, there may be no information about non-basic CORESET configuration parameters in the NR-PBCH. Alternatively, for other non-basic CORESET configuration parameters, a "default" mode may be used. For example, the default pattern may include information such as a frequency-first mapping or a time-first mapping of REG-CCE mapping. In some embodiments, the frequency first mapping may be defined as a default mode and may be fixed. In some embodiments, an Antenna Port (AP) based transmit diversity may be defined as a "default" transmission scheme, and other modes may be indicated in the RMSI. The NR-PDCCH in the common CORESET for EMSI, RMSI, or oSI and for scheduling of RAR messages, Msg3 retransmissions, or Msg4 scheduling may be specified to follow a distributed CCE to REG mapping for the NR-PDCCH. In this embodiment, in order for the UE to receive the NR-PDCCH transmission to receive the RMSI, the UE may use "basic" CORESET configuration parameters and a default mode.

In some embodiments, if the UE receives the RMSI, the UE may be able to identify the "non-basic" CORESET configuration parameters as well as the "basic" CORESET configuration parameters, and may be able to use these parameters for the reception of the NR-PDCCH in CORESET thereafter. In some embodiments, a "basic" core set may be a subset of a "non-basic" core set, either in terms of time or frequency resources or in terms of transmitted parameters. In some embodiments, a "basic" core set may not overlap with a "non-basic" core set or may partially overlap with a "non-basic" core set. In one embodiment, the "basic" core and "non-basic" core may be configured in different bandwidth portions.

In some embodiments, a "basic" CORESET may be used for NR-PDCCH transmissions including information related to scheduling RMSI, oSI, or another common control message (e.g., paging information or RAR). Alternatively, a "basic" core set may be used for NR-PDCCH transmissions that include only information related to the scheduled RMSI, while a "non-basic" core set or the entire core set may be used for NR-PDCCH transmissions that include information related to the schedule oSI or some other common control message such as paging information or RARs. As used herein, "entire" CORESET may refer to both "basic" and "non-basic" CORESET.

In some embodiments, even for the CORESET size and location, the NR-PBCH transmission may indicate only a portion of the entire CORESET, and the RMSI may indicate detailed information about the size and location of the entire CORESET. The CORESET size or location information in the NR-PBCH can be further minimized. For example, table 1 may be used, where 3 bits may be sufficient to indicate CORESET size or position. However, other embodiments may use different ways to indicate the "basic" CORESET configuration parameters with a minimized number of bits.

Frequency band size CORESET span	Frequency location	Number of OFDM symbols
			5 MHz (MHz)	4 cases	2
10MHz	2 cases	2
			20MHz	1	1
40MHz	1	1

Table 1

In addition, different common CORESET may be mapped to different Bandwidth (BW) portions, which may or may not overlap, based on the possible configuration of the BW portions in the cell. For example, the common CORESET for RAR/Msg3/Msg4, and in some embodiments oSI scheduling, may be in a different BW portion than the BW portion, which may include information related to scheduling EMSI or RMSI. The UE may monitor the NR-PDCCH in the common CORESET mapped to different BW portions in connection with scheduling of paging records. Such a configuration may typically be used in systems with UEs that may support limited BW as compared to system BW.

Fig. 6 illustrates an example CORESET transmission in an NR slot 600 in accordance with various embodiments. The NR slot 600 may be composed of several OFDM symbols 620. Although only 8 OFDM symbols 620 are depicted in fig. 6, in other embodiments the NR slot 600 may include more or fewer OFDM symbols, such as 14 symbols or some other number.

The "basic" CORESET 605 may be sent in a first set of resources. As shown in fig. 6, the first set of resources may include a single OFDM symbol 620 and span several frequency subcarriers. The "non-base" CORESET may then be sent. In embodiments, a "non-base" CORESET may be as shown at 610, and at least partially overlap with "base" CORESET 605. For example, the "non-base" core set 610 overlaps the "base" core set 605 in both time and frequency resources, but also includes additional resources in both time and frequency. In other embodiments, the "non-base" core may additionally or alternatively be a "non-base" core 615 that does not overlap with the "base" core 605.

As described above, the entire CORESET may be considered to be a "base" CORESET 605 and one or both of "non-base" CORESETs 610 and 615. In general, as described above, configuration information for the "basic" core set 605 may be sent in the NR-PBCH transmission and include information on the following resources: the UE may identify subsequent transmissions of "basic" CORESET on these resources in order to receive the NR-PDCCH or NR-PDSCH of RMSI or oSI, and configuration information of "non-basic" CORESET 610 or 615 may be transmitted in RMSI or oSI, as described above.

Note that as shown in fig. 6, a "base" core may be a subset of the entire or "non-base" core. As a further extension, the search space defined in "basic" CORESET may be a subset of the search space defined for the entire CORESET.

In another embodiment, a two-step CORESET configuration may be used. To receive the RMSI, the UE may monitor the NR-PDCCH and receive a corresponding NR-PDCCH transmission. Thus, for reception of a NR-PDCCH transmission, the NR-PBCH may indicate to the UE which resource to monitor. To reduce the configuration information included in the NR-PBCH, only "basic" core configuration information may be included in the NR-PBCH. Other configuration information may be included in the RMSI or other system information.

Among the various parameters described above, only the "basic" parameter may be included in the NR-PBCH transmission, and the remaining parameters may be included in oSI. In this embodiment, in order for the UE to receive the NR-PDCCH transmission before receiving the "non-basic" core set configuration information from oSI, the UE may use the "basic" core set configuration parameters and default mode as described above. If the UE receives oSI, it may then know all or some "non-basic" CORESET configuration parameters as well as "basic" CORESET configuration parameters, and it may use these parameters for the reception of NR-PDCCH in CORESET thereafter. For this case, the configuration of the CORESET and search space for NR-PDCCH scheduling for RAR, Msg3, Msg4, etc. may be the same as indicated via the NR-PBCH "basic" CORESET parameter transmission.

In another embodiment, a multi-step CORESET configuration may be used. In this embodiment, there may be multiple steps for the indication of the CORESET configuration parameters. The UE may operate in a default mode before receiving the specific CORESET configuration parameters. If the CORESET configuration parameters are received in the NR-PBCH transmission, in the RMSI, in a oSI transmission such as an oSI-1 or oSI-2 transmission, or in some other transmission, the UE may use this information after it is received.

In another embodiment, the NR-PBCH may indicate a Physical Random Access Channel (PRACH) format for a cell to which the UE is communicatively coupled. To reduce the information bits in NR-PBCH transmissions, the PRACH format may indicate a set of parameters, including subcarrier spacing, for NR-PDCCH transmission for RMSI reception and for NR-PDCCH for random access procedures. Since there are multiple PRACH formats including multiple subcarrier spacings, there may be a mapping between PRACH formats and subcarrier spacings for reception of RMSI or NR-PDCCH transmission for random access procedures.

In another embodiment, the NR-PBCH transmission may indicate a PRACH format for a cell to which the UE is communicatively coupled. To reduce the information bits in the NR-PBCH, the combination of the PRACH format and the default set of parameters on the cell may indicate the set of parameters, including the subcarrier spacing, of the NR-PDCCH transmission for RMSI reception and the NR-PDCCH for the random access procedure. In this embodiment, a "default set of parameters" may refer to a set of parameters for the synchronization signal so that the UE knows the parameters of the synchronization signal before receiving the synchronization signal.

Fig. 7 illustrates an example technique for transmitting control parameters, in accordance with various embodiments. In an embodiment, the technique can include, at 705, transmitting, by a base station, an indication of a first set of parameters related to a control channel. The first set of parameters may be, for example, the "basic" CORESET parameters described above. In an embodiment, the first set of parameters may be sent in a NR-PBCH transmission. In some embodiments, the first set of parameters may relate to a first set of timing parameters that may be used by the UE to monitor for control channel transmissions.

The technique can also include transmitting, by the base station, an indication of a second set of parameters related to the control channel using the first set of parameters, at 710. In some embodiments, the control channel transmission may be an NR-PDCCH transmission and may relate to an NR-PDSCH transmission including the remaining RMSIs. In some embodiments, the second set of parameters may relate to timing information, such as non-basic CORESET information, which may be used by the UE to monitor subsequent control channel transmissions. Subsequent control channel transmissions may include, for example, oSI or other control channel information.

Fig. 8 illustrates an alternative example technique for generating interleaved PDCCH transmissions, in accordance with various embodiments. In an embodiment, the technique may include sending, at 805, an indication of a first set of parameters related to PDCCH transmissions in PBCH transmissions. The PBCH transmission may be an NR-PBCH transmission and the PDCCH transmission may be an NR-PDCCH transmission. In an embodiment, the first set of parameters may be timing parameters related to NR-PDCCH transmission. The indication of the first set of parameters may be, may include, or may be related to, an eMSI as described above, and may include "basic" CORESET parameters.

The technique can also include identifying, by the base station, a first parameter related to REGB for an interleaved PDCCH transmission, where the first parameter is selected from a first plurality of parameters, at 810. The first plurality of parameters may include, for example, the number of stages of the interleaver, the interleaving unit in terms of the number of REGBs (for a given stage), the number of rows or columns of the interleaving matrix used by the interleaver or stages of the interleaver, a column permutation pattern, some other parameter, or some combination of the above.

The technique may also include interleaving, at 815, the REGB by the base station based on the first parameter to form the CCE. Examples of such interleaving may be, for example, as described above with reference to fig. 1-3.

The technique can also include transmitting, by the base station, the CCE in the PDCCH transmission at 820. In an embodiment, the sending may be performed according to the first set of parameters sent at 805. In an embodiment, the CCE may relate to an indication of a second parameter of the PDCCH. The second set of parameters may be, for example, timing information that may be used by the UE to monitor subsequent NR-PDCCH or NR-PDSCH transmissions.

It will be understood that the above-described techniques are intended to be examples. In some embodiments, certain elements may be removed or replaced. Some embodiments of the techniques herein may also have additional elements.

Fig. 9 illustrates an architecture of a system XQ00 of a network, according to some embodiments. The system XQ00 is shown to include a User Equipment (UE) XQ01 and a UE XQ 02. As used herein, the term "user equipment" or "UE" may refer to a device having radio communication capabilities and may describe a remote user of network resources in a communication network. The term "user equipment" or "UE" may be considered synonymous with, and may be referred to as: a client, a mobile phone, a mobile device, a mobile terminal, a user terminal, a mobile unit, a mobile station, a mobile user, a subscriber, a user, a remote station, an access agent, a user agent, a receiver, a radio device, a reconfigurable mobile device, and the like. In addition, the terms "user equipment" or "UE" may include any type of wireless/wired device or any computing device that includes a wireless communication interface. In this example, UEs XQ01 and XQ02 are shown as smart phones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as consumer electronics, cellular phones, smart phones, feature phones, tablet computers, wearable computer devices, Personal Digital Assistants (PDAs), pagers, wireless handsets, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-vehicle entertainment (ICE) devices, Instrument Cluster (IC), head-up display (HUD) devices, on-board diagnostics (mdondiagnostic, OBD) devices, tablet mobile Devices (DME), mobile data terminals (mobile) data, mobile data terminals (DME), and mobile computing devices, An Electronic Engine Management System (EEMS), an Electronic/Engine Control Unit (ECU), an Electronic/Engine Control Module (ECM), an embedded System, a microcontroller, a control module, an Engine Management System (EMS), a networked or "smart" appliance, a machine-type communication (MTC) device, a machine-to-machine (M2M), an Internet of Things (IoT) device, and so on.

In some embodiments, any of the UE XQs 01 and XQ02 may include Internet of Things (IoT) UEs, which may include a network access stratum designed for low power IoT applications that utilize short-term UE connections. IoT UEs may utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) to exchange data with MTC servers or devices via Public Land Mobile Networks (PLMNs), Proximity-Based services (ProSe) or device-to-device (D2D) communications, sensor networks, or IoT networks. The M2M or MTC data exchange may be a machine initiated data exchange. IoT network descriptions utilize short-term connections to interconnect IoT UEs, which may include uniquely identifiable embedded computing devices (within the internet infrastructure). The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connection of the IoT network.

The UEs XQ01 and XQ02 may be configured to connect, e.g., communicatively couple, with a Radio Access Network (RAN) XQ 10. The RAN XQ10 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) terrestrial radio Access Network (E-UTRAN), a next generation RAN (NG RAN), or some other type of RAN. The UEs XQ01 and XQ02 utilize connections (or channels) XQ03 and XQ04, respectively, each of the connections (or channels) XQ03 and XQ04 comprising a physical communication interface or layer (discussed in more detail below). As used herein, the term "channel" may refer to any transmission medium, whether tangible or intangible, for transmitting data or data streams. The term "channel" may be synonymous and/or equivalent to "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," and/or any other similar term referring to a channel or medium through which data is transmitted. Furthermore, the term "link" may refer to a connection between two devices through a Radio Access Technology (RAT) for transmitting and receiving information. In this example, connections XQ03 and XQ04 are shown as air interfaces to enable communicative coupling, and may conform to a Cellular communication protocol, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a Cellular PTT (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation (fifth generation, 5G) protocol, a New Radio (New Radio, NR) protocol, and so forth.

In this embodiment, the UEs XQ01 and XQ02 may also exchange communication data directly via the ProSe interface XQ 05. The ProSe interface XQ05 may alternatively be referred to as a Sidelink (SL) interface including one or more logical channels, including, but not limited to, a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (psch), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH). In various implementations, the SL interface XQ05 may be used in vehicle applications and communication technologies, often referred to as V2X systems. V2X is a communication mode in which UEs (e.g., UEs XQ01, XQ02) communicate directly with each other over PC5/SL interface XQ05, and may occur when UEs XQ01, XQ02 are served by RAN nodes XQ11, XQ12 or when one or more UEs are outside the coverage area of RAN XQ 10. V2X can be classified into four different types: vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), and vehicle-to-pedestrian (V2P). These V2X applications may use "collaborative awareness" to provide more intelligent services to end users. For example, vehicle UE (vue) XQ01, XQ02, RAN nodes XQ11, XQ12, application server XQ30 and pedestrian UEs XQ01, XQ02 may collect knowledge of their local environment (e.g., information received from other vehicles or sensor devices in the vicinity) to process and share that knowledge in order to provide more intelligent services, such as collaborative collision warning, autonomous driving, and so forth. In these implementations, the UEs XQ01, XQ02 may be implemented/used as Vehicle Embedded Communications Systems (VECS) or vUE.

The UE XQ02 is shown configured to access via a connection XQ07Point (AP) XQ06 (also referred to as WLAN node XQ06, WLAN XQ06, WLAN termination XQ06, WT XQ06, and the like). The connection XQ07 may comprise a local wireless connection, such as a connection conforming to any IEEE 802.11 protocol, where the AP XQ06 would include wireless fidelityA router. In this example, the AP XQ06 is shown as being connected to the internet, rather than to the core network of the wireless system (described in more detail below). In various embodiments, the UE XQ02, RAN XQ10, and AP XQ06 may be configured to utilize LTE-WLAN aggregation (LWA) operations and/or Radio Level Integration (LWIP) operations of WLAN LTE/WLAN over IPsec tunnels. LWA operation may involve the UE XQ02 being in RRC _ CONNECTED being configured by RAN nodes XQ11, XQ12 to utilize the radio resources of LTE and WLAN. LWIP operations may involve the UE XQ02 utilizing WLAN radio resources (e.g., connection XQ07) to authenticate and encrypt packets (e.g., Internet Protocol (IP) packets) sent over the connection XQ07 via Internet protocol security (IPsec) protocol tunneling. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

The RAN XQ10 may include one or more access nodes that enable connection of the XQ03 and the XQ 04. As used herein, the terms "access node," "access point," and the like may describe a device that provides radio baseband functionality for data and/or voice connectivity between a network and one or more users. As described above, these access nodes may be referred to as Base Stations (BSs), nodebs, evolved nodebs (enbs), next generation nodebs (gnbs), RAN nodes, RoadSide units (RSUs), and so on, and may include ground stations (e.g., ground access points) or satellite stations that provide coverage within a certain geographic area (e.g., a cell). The term "roadside unit" or "RSU" may refer to any transport infrastructure entity implemented in or by a gNB/eNB/RAN node or a fixed (or relatively fixed) UE, where an RSU implemented in or by a UE may be referred to as a "UE-type RSU," and an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU" RANXQ10 may include one or more RAN nodes, such as a macro RAN node XQ11, for providing a macro cell, and one or more RAN nodes, such as a Low Power (LP) RAN node XQ12, for providing a femto cell or pico cell (e.g., a cell having a smaller coverage area, smaller user capacity, or higher bandwidth than a macro cell).

Any of the RAN nodes XQ11 and XQ12 may terminate the air interface protocol and may be the first contact point for UEs XQ01 and XQ 02. In some embodiments, any of the RAN nodes XQ11 and XQ12 may perform various logical functions for the RAN XQ10, including but not limited to Radio Network Controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

According to some embodiments, UEs XQ01 and XQ02 may be configured to communicate with each other or with any of RAN nodes XQ11 and XQ12 using Orthogonal Frequency Division Multiplexing (OFDM) communication signals over a multicarrier communication channel according to various communication techniques, such as, but not limited to, Orthogonal Frequency-Division Multiple Access (OFDMA) communication techniques (e.g., for downlink communications) or Single Carrier Frequency Division Multiple Access (SC-FDMA) communication techniques (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signal may include a plurality of orthogonal subcarriers.

In some embodiments, the downlink resource grid may be used for downlink transmissions from any of the RAN nodes XQ11 and XQ12 to UEs XQ01 and XQ02, while uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid, referred to as a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot. This time-frequency plane representation is a common practice of OFDM systems, which makes it intuitive for radio resource allocation. Each column and first row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one time slot in a radio frame. The smallest time-frequency unit in the resource grid is denoted as a resource element. Each resource grid comprises several resource blocks, which describe the mapping of a particular physical channel to resource elements. Each resource block comprises a set of resource elements; in the frequency domain, this may represent the minimum number of resources that are currently allocable. There are several different physical downlink channels carried with such resource blocks.

According to various embodiments, the UEs XQ01, XQ02 and the RAN nodes XQ11, XQ12 transmit data (e.g., send and receive data) over a licensed medium (also referred to as "licensed spectrum" and/or "licensed band") and an unlicensed shared medium (also referred to as "unlicensed spectrum" and/or "unlicensed band"). The licensed spectrum may include channels operating in a frequency range of about 400MHz to about 3.8GHz, while the unlicensed spectrum may include a 5GHz band.

To operate in unlicensed spectrum, the UEs XQ01, XQ02 and RAN nodes XQ11, XQ12 may operate with Licensed Assisted Access (LAA), enhanced LAA (eLAA) and/or further eLAA (femto eLAA) mechanisms. In these implementations, the UEs XQ01, XQ02 and the RAN nodes XQ11, XQ12 may perform one or more known medium sensing operations and/or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied prior to transmission in the unlicensed spectrum. The media/carrier sensing operation may be performed according to the listen-before-talk (LBT) protocol.

LBT is a mechanism by which devices (e.g., UEs XQ01, XQ02, RAN nodes XQ11, XQ12, etc.) detect a medium (e.g., a channel or carrier frequency) and transmit when the medium is detected to be idle (or when it is detected that a particular channel in the medium is unoccupied). The medium detection operation may include Clear Channel Assessment (CCA) that utilizes at least Energy Detection (ED) to determine the presence or absence of other signals on the channel in order to determine whether the channel is occupied or clear. This LBT mechanism allows cellular/LAA networks to coexist with incumbent systems in unlicensed spectrum and with other LAA networks. ED may include detecting Radio Frequency (RF) energy over an expected transmission band for a period of time and comparing the detected RF energy to a predetermined or configured threshold.

Generally, an incumbent system in the 5GHz band is a WLAN based on IEEE 802.11 technology. WLANs employ a contention-based channel access mechanism known as carrier sense multiple access with collision avoidance (CSMA/CA). Here, when a WLAN node (e.g., a Mobile Station (MS) such as UE XQ01 or XQ02, AP 106, etc.) wants to transmit, the WLAN node may first perform a CCA before transmitting. Furthermore, a back-off mechanism is used to avoid collisions when more than one WLAN node detects a channel as idle and transmits at the same time. The back-off mechanism may be a counter that is randomly drawn within a Contention Window Size (CWS), is exponentially increased when a collision occurs, and is reset to a minimum value when a transmission is successful. The LBT mechanism designed for LAA is sometimes similar to CSMA/CA of WLAN. In some implementations, an LBT procedure including DL or UL transmission bursts of PDSCH or Physical Uplink Shared Channel (PUSCH) transmissions, respectively, may have an LAA contention window of variable length between X and Y extended cca (ecca) slots, where X and Y are minimum and maximum values of a CWS for LAA. In one example, the minimum CWS for LAA transmission may be 9 microseconds (μ s); however, the size of the CWS and the Maximum Channel Occupancy Time (MCOT) (e.g., send burst) may be based on government regulatory requirements.

The LAA mechanism is built on Carrier Aggregation (CA) technology of LTE advanced systems. In CA, each aggregated carrier is called a Component Carrier (CC). The CCs may have bandwidths of 1.4, 3, 5, 10, 15, or 20MHz and up to five CCs may be aggregated, and thus the maximum aggregated bandwidth is 100 MHz. In a Frequency Division Duplex (FDD) system, the number of aggregated carriers may be different for DL and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers. In some cases, individual CCs may have different bandwidths than other CCs. In a Time Division Duplex (TDD) system, the number of CCs and the bandwidth of each CC are generally the same for DL and UL.

The CA also includes individual serving cells to provide individual CCs. The coverage of the serving cell may differ, for example, because CCs on different frequency bands will experience different path losses. A primary serving cell or primary cell (PCell) may provide a primary cc (pcc) for both UL and DL and may handle Radio Resource Control (RRC) and Non-Access Stratum (NAS) related activities. Other serving cells are referred to as secondary cells (scells), and each SCell may provide an individual secondary cc (scc) for both UL and DL. SCCs may be added and removed as needed, while changing PCCs may require UEs XQ01, XQ02 to undergo handovers. In LAA, eLAA, and feLAA, some or all scells may operate in unlicensed spectrum (referred to as "LAA scells"), and the LAA scells may be assisted by pcells operating in licensed spectrum. When the UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCell, which indicate different PUSCH starting positions within the same subframe.

A Physical Downlink Shared Channel (PDSCH) may carry user data and higher layer signaling to UEs XQ01 and XQ 02. A Physical Downlink Control Channel (PDCCH) may carry information about a transport format and resource allocation related to a PDSCH channel, and the like. It may also inform UEs XQ01 and XQ02 about transport format, resource allocation, and H-ARQ (hybrid automatic repeat request) information related to the uplink shared channel. In general, downlink scheduling (assigning control and shared channel resource blocks to UE XQ02 within a cell) may be performed at any of RAN nodes XQ11 and XQ12 based on channel quality information fed back from any of UE XQ01 and XQ 02. The downlink resource assignment information may be sent on PDCCH for (e.g., assigned to) each of UE XQ01 and XQ 02.

The PDCCH may use a Control Channel Element (CCE) to carry control information. The PDCCH complex-valued symbols may first be organized into quadruplets before being mapped to resource elements, which may then be transposed with a sub-block interleaver for rate matching. Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements called Resource Element Groups (REGs). Four Quadrature Phase Shift Keying (QPSK) symbols may be mapped for each REG. Depending on the size of Downlink Control Information (DCI) and channel conditions, the PDCCH may be transmitted using one or more CCEs. There may be four or more different PDCCH formats defined in LTE, with different numbers of CCEs (e.g., aggregation level L ═ 1,2, 4, or 8).

Some embodiments may use the concept of resource allocation for control channel information, which is an extension of the above-described concept. For example, some embodiments may utilize an Enhanced Physical Downlink Control Channel (EPDCCH) that uses PDSCH resources for control information transmission. The EPDCCH may be transmitted using one or more Enhanced Control Channel Elements (ECCEs). Similar to the above, each ECCE may correspond to nine sets of four physical resource elements called Enhanced Resource Element Groups (EREGs). ECCE may have other numbers of EREGs in some cases.

The RAN XQ10 is shown communicatively coupled to a Core Network (CN) XQ20 via an S1 interface XQ 13. In embodiments, the CN XQ20 may be an Evolved Packet Core (EPC) network, a next generation Packet Core (NPC) network, or some other type of CN. In this embodiment, the S1 interface XQ13 is split into two parts: an S1-U interface XQ14 that carries traffic data between the RAN nodes XQ11 and XQ12 and the serving gateway (S-GW) XQ 22; and S1 Mobility Management Entity (MME) interface XQ15, which is a signaling interface between the RAN nodes XQ11 and XQ12 and MME XQ 21.

In this embodiment, CN XQ20 includes MME XQ21, S-GW XQ22, Packet Data Network (PDN) gateway (P-GW) XQ23, and Home Subscriber Server (HSS) XQ 24. The MME XQ21 may be similar in function to the control plane of a conventional Serving General Packet Radio Service (GPRS) Support Node (SGSN). The MME XQ21 may manage mobility aspects in access such as gateway selection and tracking area list management. HSS XQ24 may include a database for network users including subscription related information to support processing of communication sessions by network entities. The CN XQ20 may include one or several HSS XQs 24, depending on the number of mobile subscribers, the capacity of the device, the organization of the network, etc. For example, HSSXQ24 may provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location compliance, and so forth.

The S-GW XQ22 may terminate the S1 interface XQ13 towards the RAN XQ10 and route data packets between the RAN XQ10 and the CN XQ 20. In addition, the S-GW XQ22 may be a local mobility anchor for inter-RAN node handovers and may also provide an anchor for inter-3 GPP mobility. Other responsibilities may include lawful interception, charging, and some policy enforcement.

The P-GW XQ23 may terminate the SGi interface towards the PDN. The P-GW XQ23 may route data packets between the EPC network XQ20 and an external network, such as a network including an application server XQ30 (alternatively referred to as an Application Function (AF)), via an Internet Protocol (IP) interface XQ 25. In general, the application server XQ30 may be an element that provides applications that use IP bearer resources with the core network (e.g., UMTS Packet Service (PS) domain, LTE PS data services, etc.). In this embodiment, the P-GW XQ23 is shown communicatively coupled to the application server XQ30 via an IP communications interface XQ 25. The application server XQ30 may also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs XQ01 and XQ02 via CN XQ 20.

The P-GW XQ23 may also be a node for policy enforcement and charging data collection. Policy and Charging Rules Function (PCRF) XQ26 is a Policy and Charging control element of CN XQ 20. In a non-roaming scenario, there may be a single PCRF in a Home Public Land Mobile Network (HPLMN) associated with an Internet Protocol connectivity access Network (IP-CAN) session of the UE. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with the IP-CAN session of the UE: a Home PCRF (H-PCRF) within the HPLMN and a Visited PCRF (VisitedPCRF, V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF XQ26 may be communicatively coupled to the application server XQ30 via the P-GW XQ 23. The application server XQ30 may signal the PCRF XQ26 to indicate the new service flow and select the appropriate Quality of service (QoS) and charging parameters. The PCRF XQ26 may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) using an appropriate Traffic Flow Template (TFT) and QoS Class Identifier (QCI), which starts the QoS and Charging specified by the application server XQ 30.

Fig. 10 illustrates an architecture of a system XR00 of a network, in accordance with some embodiments. System XR00 is shown to include UE XR01, which may be the same as or similar to previously described UE XQ01 and XQ 02; a RAN node XR11, which may be the same as or similar to the previously described RAN nodes XQ11 and XQ 12; a Data Network (DN) XR03, which may be, for example, an operator service, internet access, or 3 rd party service; and a 5G Core Network (5G Core Network, 5GC or CN) XR 20.

CN XR20 may include Authentication Server Function (AUSF) XR 22; access and Mobility Management Function (AMF) XR 21; session Management Function (SMF) XR 24; network Exposure Function (NEF) XR 23; policy Control Function (PCF) XR 26; network Function (NF) warehouse Function (NRF) XR 25; unified Data Management (UDM) XR 27; AF XR 28; user Plane Function (UPF) XR 02; and a Network Slice Selection Function (NSSF) XR 29.

The UPF XR02 may serve as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point interconnected to DN XR03, and a branch point to support multihomed PDU sessions. The UPF XR02 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane portion of policy rules, lawful intercepted packets (UP collection), traffic usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF to QoS flow mapping), transport level packet marking in uplink and downlink, and downlink packet buffering and downlink data notification triggering. The UPF XR02 may include an uplink classifier to support routing of traffic flows to a data network. DN XR03 may represent various network operator services, internet access, or third party services. DN XR03 may include or be similar to application server XQ30 described previously. The UPF XR02 may interact with the SMF XR24 via the N4 reference point between SMF XR24 and UPF XR 02.

The AUSF XR22 may store data for authentication of the UE XR01 and process authentication related functions. AUSF XR22 may facilitate a common authentication framework for various access types. The AUSF XR22 may communicate with the AMF XR21 via the N12 reference point between AMF XR21 and AUSF XR 22; and may communicate with UDMXR27 via an N13 reference point between UDM XR27 and AUSF XR 22. Further, AUSF XR22 may expose a Nausf service-based interface.

The AMF XR21 may be responsible for registration management (e.g., for registering UE XR01, etc.), connection management, reachability management, mobility management, and lawful interception of AMF related events, as well as access authentication and authorization. The AMF XR21 may be the termination point of the N11 reference point between AMF XR21 and SMF XR 24. AMF XR21 may provide transport for Session Management (SM) messages between UE XR01 and SMF XR24 and act as a transparent proxy for routing SM messages. The AMF XR21 may also provide transport for Short Message Service (SMS) messages between the UE XR01 and an SMS function (SMSF) (not shown in fig. XR). The AMF XR21 may act as a Security anchor function (SEAF), which may include interaction with AUSF XR22 and UE XR01, as well as reception of intermediate keys established as a result of the UE XR01 authentication process. In the case of using UMTS Subscriber Identity Module (USIM) based authentication, the AMF XR21 may retrieve security materials from AUSF XR 22. AMF XR21 may also include a Security Context Management (SCM) function that receives a key from the SEAF, which is used by it to derive an access network-specific key. Further, the AMF XR21 may be a termination point of a RAN CP interface, which may include or may be AN (R) N2 reference point between AN XR11 and AN AMF XR 21; and the AMF XR21 may be a termination point for NAS (N1) signaling and perform NAS encryption and integrity protection.

The AMF XR21 may also support NAS signaling with UE XR01 over an N3 interworking-function (IWF) interface. An N3IWF may be used to provide access to untrusted entities. The N3IWF may be the termination point of the N2 interface between (R) ANXR11 and AMF XR21 for the control plane and the termination point of the N3 reference point between (R) AN XR11 and UPF XR02 for the user plane. As such, AMF XR21 may process N2 signaling from SMF XR24 and AMFXR21 for PDU sessions and QoS, tunnel encapsulated/decapsulated packets for IPSec and N3, tag N3 user plane packets in the uplink, and implement QoS corresponding to N3 packet tagging, which may take into account QoS requirements associated with such tagging received over N2. The N3IWF may also relay uplink and downlink control plane NAS signaling between UE XR01 and AMF XR21 and uplink and downlink user plane packets between UE XR01 and UPF XR02 via an N1 reference point between UE XR01 and AMF XR 21. The N3IWF also provides a mechanism for IPsec tunnel establishment with UE XR 01. The AMF XR21 may expose a Namf service-based interface and may be a termination point for the N14 reference point between two AMFs XR21 and an N17 reference point between AMF XR21 and a 5G Equipment Identity registrar (5G-Equipment Identity Register, 5G-EIR) (not shown in fig. XR).

The SMF XR24 may be responsible for session management (e.g., session establishment, modification, and release, including tunnel maintenance between UPF and AN nodes). The SMF XR24 may also assign and manage UE IP addresses (including optional authorizations), select and control UP functions, and configure traffic handling at the UPF XR02 to route traffic to the appropriate destination. SMF XR24 may also terminate the interface towards the policy control function, control part of the policy enforcement and QoS, and perform lawful interception (e.g., for SM events and interface to the LI system). The SMF XR24 may also terminate the SM portion of the NAS message, provide downlink data notification, and initiate AN-specific SM message sent over N2 to the AN via the AMF, and determine the Session and the Session's Service Continuity (SSC) pattern.

SMF XR24 may include the following roaming functions: processing the local enforcement to apply a QoS SLA (VPLMN); a charging data collection and charging interface (VPLMN); lawful interception (in VPLMN, for SM events and interface to LI system); and support for interaction with the foreign DN for transmitting signaling for PDU session authorization/authentication by the foreign DN. An N16 reference point between two SMF XR24 may be included in the system XR00, which in a roaming scenario may be between another SMFXR24 in the visited network and the SMF XR24 in the home network. Further, SMF XR24 may expose an Nsmf service-based interface.

NEF XR23 may provide a means for securely exposing services and capabilities provided by 3GPP network functions, internal exposure/re-exposure, application functions (e.g., AF XR28), edge computing or fog computing systems, and the like for third parties. In such embodiments, NEF XR23 may authenticate, authorize, and/or throttle AF. NEF XR23 may also translate information exchanged with AF XR28 and information exchanged with internal network functions. For example, NEF XR23 may translate between AF service identifiers and internal 5GC information. Nexfr 23 may also receive information from other Network Functions (NFs) based on exposed capabilities of the other network functions. This information may be stored as structured data at NEF XR23, or at data store NF using a standardized interface. The stored information may then be re-exposed to other NFs and AFs by NEF XR23, and/or used for other purposes, such as parsing. Further, NEF XR23 may expose a Nnef service-based interface.

NRF XR25 may support a service discovery function, receive NF discovery requests from NF instances, and provide information of discovered NF instances to NF instances. NRF XR25 also maintains information on available NF instances and the services it supports. As used herein, the term "instantiation" or the like may refer to the creation of an instance, and "instance" may refer to the specific occurrence of an object, which may occur, for example, during execution of program code. Further, NRF XR25 may expose a Nnrf service-based interface.

PCF XR26 may provide policy rules to the control plane function(s) to enforce them, and may also support a unified policy framework to constrain network behavior. The PCF XR26 may also implement a Front End (FE) to access subscription information related to policy decisions in a Unified Data Repository (UDR) of UDMXR 27. The PCF XR26 may communicate with the AMF XR21 via the N15 reference point between PCF XR26 and AMF XR21, which may include between PCF XR26 and AMF XR21 in the visited network in the case of roaming scenarios. PCF XR26 may communicate with AF XR28 via the N5 reference point between PCF XR26 and AFXR 28; and communicates with the SMFXR24 via the N7 reference point between the PCF XR26 and the SMF XR 24. The system XR00 and/or CN XR20 may also include an N24 reference point between the PCF XR26 (in the home network) and the PCFXR26 in the visited network. Further, PCF XR26 may expose a Npcf service-based interface.

The UDM XR27 may process subscription-related information to support processing of communication sessions by network entities and may store subscription data for the UE XR 01. For example, subscription data may be transmitted between the UDMXR27 and the AMF XR21 via an N8 reference point between the UDM XR27 and the AMF XR21 (not shown in fig. XR). UDM XR27 may include two portions: an application FE and a User Data Repository (UDR) (FE and UDR are not shown in fig. XR). The UDR may store subscription data and policy data for UDM XR27 and PCF XR26, and/or structured data and application data for exposure for NEF XR23 (including Packet Flow Description (PFD) for application detection, application request information for multiple UEs XR 01). The Nudr service-based interface can be exposed by the UDR to allow the UDM XR27, PCF XR26, and NEF XR23 to access a particular set of stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notifications of relevant data changes in the UDR. The UDM XR27 may include a UDM FE that is responsible for handling certificates, location management, subscription management, and the like. 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 processing; access authorization; registration/mobility management; and subscription management. The UDR may interact with SMF XR24 via the N10 reference point between UDM XR27 and SMF XR 24. UDM XR27 may also support SMS management, where the SMS-FE implements similar application logic as previously described. Further, UDM XR27 may expose a Nndm service-based interface.

The AF XR28 may provide application impact on traffic routing, provide access to Network Capability Exposure (NCE), and interact with the policy framework for policy control. NCE may be a mechanism that allows 5GC and AF XR28 to provide information to each other via NEF XR23 that may be used in edge computing implementations. In such an implementation, the attachment access point, which may be close to the UE XR01, hosts network operator and third party services to enable efficient service delivery with reduced end-to-end latency and load on the transport network. For edge calculation implementations, the 5GC may select a UPF XR02 close to the UE XR01 and perform traffic steering from the UPF XR02 to the DN XR03 via the N6 interface. This may be based on UE subscription data, UE location and information provided by the AF XR 28. As such, AF XR28 may affect UPF (re) selection and traffic routing. Based on operator deployment, the network operator may allow the AF XR28 to interact directly with the relevant NFs when the AF XR28 is considered a trusted entity. Further, the AF XR28 may expose a Naf service-based interface.

NSSF XR29 may select a set of network slice instances that serve UE XR 01. The NSSF XR29 may also determine allowed Network Slice Selection Assistance Information (NSSAI) and a mapping to a single NSSAI (S-NSSAI) of the subscription, if desired. The NSSF XR29 may also determine the set of AMFs to be used to serve the UE XR01, or a list of candidate AMFs XR21, based on an appropriate configuration and possibly by querying the NRF XR 25. The selection of a set of network slice instances for the UE XR01 may be triggered by the AMF XR21 with which the UE XR01 is registered through interaction with the NSSF XR29, which may result in a change in the AMF XR 21. NSSF XR29 may interact with AMF XR21 via the N22 reference point between AMFXR21 and NSSF XR 29; and may communicate with another NSSF XR29 in the visited network via an N31 reference point (not shown in fig. XR). Further, NSSF XR29 may expose an NSSF service-based interface.

As previously described, CN XR20 may include SMSF, which may be responsible for SMS subscription checking and verification, and relaying SM messages from UE XR01 to/from other entities to UE XR01, such as Short Message Service (SMS) -Global system for Mobile Communication (GMSC)/Interworking Mobile Switching Center (IWMSC)/SMS-router. SMS may also interact with AMFXR21 and UDM XR27 to perform notification procedures regarding UE XR01 as available for SMS delivery (e.g., set UE unreachable flag and notify UDM XR27 when UE XR01 is available for SMS).

CN XR20 may also include other elements not shown in fig. XR, such as a data storage system/architecture, a 5G device identity registrar (5G-EIR), a Security Edge Protection Proxy (SEPP), and so forth. Data Storage systems may include Structured Data Storage network functions (SDSF), Unstructured Data Storage network functions (UDSF), and so forth. Any NF may store and retrieve unstructured data (e.g., UE context) into and from the UDSF via the N18 reference point between any NF and the UDSF (not shown in fig. XR). The individual NFs may share the UDSF to store their respective unstructured data, or the individual NFs may each have their own UDSF located at or near the individual NFs. Further, the UDSF may expose a Nudsf service-based interface (not shown in fig. XR). The 5G-EIR may be an NF that checks the status of a permanent device Identifier (PEI) to determine if a particular device/entity is blacklisted from the network; and SEPP may be a non-transparent proxy that performs topology hiding, message filtering, and policy enforcement on inter-PLMN control plane interfaces.

Furthermore, there may be more other reference points and/or service-based interfaces between NF services in the NF; however, these interfaces and reference points have been omitted from the XR diagram for clarity. In one example, CN XR20 may include an Nx interface, which is an inter-CN interface between an MME (e.g., MME XQ21) and AMF XR21 to enable interworking between CN XR20 and CN XQ 20. Other example interfaces/reference points may include the N5G-EIR service-based interface exposed by the 5G-EIR, the N27 reference point between the NRF in the visited network and the NRF in the home network; and an N31 reference point between the NSSF in the visited network and the NSSF in the home network.

In another example, the system XR00 may include multiple RAN nodes XR11, where an Xn interface is defined between two or more RAN nodes XR11 (e.g., gNB, etc.) connected to the 5GC XR20, between a RAN node XR11 (e.g., gNB) and an eNB (e.g., RAN node XQ11 of fig. XQ) connected to the 5GC XR20, and/or between two enbs connected to the 5GC XR 20. In some implementations, the Xn interface can include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide for non-guaranteed delivery of user plane PDUs and support/provide data forwarding and flow control functionality. Xn-C may provide management and error handling functions, managing the functionality of the Xn-C interface; and mobility support for the UE XR01 in CONNECTED mode (e.g., CM-CONNECTED), including functionality to manage UE mobility for CONNECTED mode between one or more RAN nodes XR 11. Mobility support may include context transfer from the old (source) serving RAN node XR11 to the new (target) serving RAN node XR 11; and control of user-plane tunnels between the old (source) serving RAN node XR11 to the new (target) serving RAN node XR 11. The Protocol stack of the Xn-U may include a transport network layer built on top of an Internet Protocol (IP) transport layer and a GTP-U layer on top of UDP and/or IP layer(s) to carry user plane PDUs. The Xn-C Protocol stack may include an Application layer signaling Protocol, referred to as Xn Application Protocol (Xn-AP), and a transport network layer built on the SCTP layer. The SCTP layer can be above the IP layer. The SCTP layer provides guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transport is used to deliver signaling PDUs. In other implementations, the Xn-U protocol stack and/or the Xn-C protocol stack may be the same as or similar to the user plane and/or control plane protocol stack(s) shown and described herein.

Fig. 11 illustrates an example of infrastructure equipment XS00, in accordance with various embodiments. The infrastructure equipment XS00 (or "system XS 00") may be implemented as base stations, radio heads, RAN nodes, etc., such as the RAN nodes XQ11 and XQ12 and/or AP XQ06 shown and described previously. In other examples, system XS00 may be implemented in or by a UE, application server(s) XQ30, and/or any other element/device discussed herein. The system XS00 may include one or more of the following: application circuit XS05, baseband circuit XS10, one or more radio front-end modules XS15, memory XS20, Power Management Integrated Circuit (PMIC) XS25, power tee circuit XS30, network controller XS35, network interface connector XS40, satellite positioning circuit XS45, and user interface XS 50. In some embodiments, device XT00 may include additional elements such as memory/storage, displays, cameras, sensors, or input/output (I/O) interface elements. In other embodiments, the components described below may be included in more than one device (e.g., for a cloud RAN (C-RAN) implementation, the circuitry may be included separately in more than one device).

As used herein, the term "circuitry" may refer to, be part of, or include hardware components such as the following configured to provide the described functionality: electronic circuits, logic circuits, processors (shared, dedicated, or group) and/or memories (shared, dedicated, or group), Application Specific Integrated Circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs)), Programmable Logic Devices (PLDs), complex PLDs (complex PLDs, CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable system on chips (socs)), Digital Signal Processors (DSPs), and so forth. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. Furthermore, the term "circuitry" may also refer to a combination of one or more hardware elements (or circuitry used in an electrical or electronic system) and program code for performing the functions of the program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

The terms "application circuitry" and/or "baseband circuitry" may be considered synonymous with "processor circuitry" and may be referred to as "processor circuitry". As used herein, the term "processor circuit" may refer to, be part of, or include circuitry that: the circuit is capable of sequentially and automatically performing a sequence of arithmetic or logical operations; and recording, storing and/or transmitting digital data. The term "processor circuit" may refer to one or more application processors, one or more baseband processors, physical Central Processing Units (CPUs), single-core processors, dual-core processors, tri-core processors, quad-core processors, and/or any other device capable of executing or otherwise manipulating computer-executable instructions, such as program code, software modules, and/or functional processes.

Further, various components of the core network XQ20 (or CN XR20 as previously discussed) may be referred to as "network elements. The term "network element" may describe a physical or virtualized device used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with and/or referred to as: a networking computer, networking hardware, network device, network node, router, switch, hub, bridge, radio network controller, radio access network device, gateway, server, Virtualized Network Function (VNF), Network Function Virtualization Infrastructure (NFVI), and so forth.

The application circuit XS05 may include one or more Central Processing Unit (CPU) cores and one or more of the following: cache memory, low drop-out (low drop-out)t, LDO) voltage regulator, an interrupt controller, a Serial Interface such as SPI, I2C, or a Universal programmable Serial Interface module, a Real Time Clock (RTC), a timer-counter including interval and watchdog timers, a Universal input/output (I/O or IO), a memory card controller such as a Secure Digital (SD)/multimedia card (MMC), a Universal Serial Bus (USB) Interface, a Mobile Industry Processor Interface (MIPI) Interface, and a Joint Test Access Group (JTAG) Test access port. As an example, the application circuit XS05 may include one or more IntelsOrA processor; ultramicron semiconductor (Advanced Micro Devices, AMD)A processor, an Accelerated Processing Unit (APU), orA processor; and so on. In some embodiments, system XS00 may not utilize application circuitry XS05, but may instead include, for example, a dedicated processor/controller to process IP data received from the EPC or 5 GC.

Additionally or alternatively, the application circuit XS05 may include circuits such as (but not limited to) the following: one or more Field Programmable Devices (FPDs), such as Field Programmable Gate Arrays (FPGAs), etc.; programmable Logic Devices (PLDs), such as complex PLDs (cplds), high capacity PLDs (hcplds), and the like; ASICs, such as structured ASICs and the like; programmable soc (psoc); and so on. In such embodiments, the circuitry of application circuitry XS05 may comprise a logic block or logic architecture, including other interconnected resources, that may be programmed to perform various functions, such as the processes, methods, functions, etc. of the various embodiments discussed herein. In such embodiments, the circuitry of the application circuit XS05 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., Static Random Access Memory (SRAM), antifuse, etc.) for storing logic blocks, logic architectures, data, etc. in a lookup table (LUT), and so forth.

Baseband circuitry XS10 may be implemented, for example, as a solder-in substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits. Although not shown, baseband circuitry XS10 may include one or more digital baseband systems that may be coupled to a CPU subsystem, an audio subsystem, and an interface subsystem via an interconnection subsystem. The digital baseband subsystem may also be coupled to the digital baseband interface and the mixed signal baseband subsystem via additional interconnect subsystems. Each interconnection subsystem may include a bus system, a point-to-point connection, a Network On Chip (NOC) fabric, and/or some other suitable bus or interconnection technology, such as those discussed herein. The audio subsystem may include digital signal processing circuitry, buffer memory, program memory, voice processing accelerator circuitry, data converter circuitry such as analog-to-digital and digital-to-analog converter circuitry, analog circuitry including one or more amplifiers and filters, and/or other similar components. In an aspect of the disclosure, the baseband circuitry XS10 may include protocol processing circuitry with one or more instances of control circuitry (not shown) to provide control functions for digital baseband circuitry and/or radio frequency circuitry (e.g., radio front end module XS 15).

The user interface circuitry XS50 may include one or more user interfaces designed to enable user interaction with the system XS00 or peripheral component interfaces designed to enable interaction with peripheral components of the system XS 00. The user interface may include, but is not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., a Light Emitting Diode (LED)), a physical keyboard or keypad, a mouse, a touchpad, a touch screen, a speaker or other audio emitting device, a microphone, a printer, a scanner, a headset, a display screen or display device, and so forth. The peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a Universal Serial Bus (USB) port, an audio jack, a power supply interface, and the like.

The radio front-end module (RFEM) XS15 may include a millimeter wave RFEM and one or more sub-millimeter wave Radio Frequency Integrated Circuits (RFICs). In some implementations, the one or more sub-millimeter wave RFICs may be physically separate from the millimeter wave RFEM. The RFIC may include a connection to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In alternative implementations, both millimeter-wave and sub-millimeter-wave radio functions may be implemented in the same physical radio front-end module XS 15. RFEM XS15 may include both millimeter wave and sub-millimeter wave antennas.

Memory circuitry XS20 may include one or more of the following: volatile memory including Dynamic Random Access Memory (DRAM) and/or Synchronous Dynamic Random Access Memory (SDRAM); and nonvolatile memory (NVM), including high speed electrically erasable memory (often referred to as flash memory), phase change random access memory (PRAM), Magnetoresistive Random Access Memory (MRAM), and the like, and may include data from one or more of the above-mentioned sourcesAnda three-dimensional (3D) cross point (XPOINT) memory. Memory circuit XS20 may be implemented as one or more of a solder-in package integrated circuit, a socket memory module, and a plug-in memory card.

The PMIC XS25 may include a voltage regulator, a surge protector, a power alarm detection circuit, and one or more backup power sources such as batteries or capacitors. The power alarm detection circuit may detect one or more of power down (under voltage) and surge (over voltage) conditions. Power tee circuit XS30 may provide power drawn from a network cable to provide both power supply and data connectivity to infrastructure equipment XS00 with a single cable.

The network controller circuit XS35 may provide connectivity to the network using a standard network interface protocol such as ethernet, GRE tunnel based ethernet, Multiprotocol Label Switching (MPLS) based ethernet, or some other suitable protocol. Network connectivity may be provided to/from infrastructure devices XS00 via network interface connectors XS40 using physical connections, which may be electrical (commonly referred to as "copper interconnects"), optical, or wireless. Network controller circuit XS35 may include one or more special purpose processors and/or FPGAs to communicate using one or more of the above-described protocols. In some implementations, the network controller circuitry XS35 may include multiple controllers to provide connectivity to other networks using the same or different protocols.

Positioning circuitry XS45 may include circuitry to receive and decode signals transmitted by one or more constellations of navigation satellites of a Global Navigation Satellite System (GNSS). Examples of a Navigation Satellite Constellation (or GNSS) may include the Global Positioning System (GPS) in the united states, the Global Navigation System (GLONASS) in russia, the galileo System in the european union, the beidou Navigation Satellite System in china, the regional Navigation System or the GNSS augmentation System (e.g., Navigation with indian Constellation, NAVIC), the Quasi-Zenith Satellite System (QZSS) in japan, the Satellite-Integrated Doppler orbit imaging and Radio Positioning in france (dongler) and so on), and so on. The positioning circuitry XS45 may include various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. to facilitate over-the-air (OTA) communication) to communicate with components of a positioning network (e.g., navigation satellite constellation nodes).

Nodes or satellites of the navigation satellite constellation(s) ("GNSS nodes") may provide positioning services by continuously transmitting or broadcasting GNSS signals along a line of sight, which may be used by GNSS receivers (e.g., positioning circuitry XS45 and/or positioning circuitry implemented by UEs XQ01, XQ02, etc.) to determine their GNSS positions. The GNSS signals may include a pseudo-random code (e.g., a sequence of ones and zeros) known to the GNSS receiver and a message including a time of transmission (ToT) of the code epoch (e.g., a defined point in the pseudo-random code sequence) and a GNSS node position at ToT. A GNSS receiver may monitor/measure GNSS signals transmitted/broadcast by multiple GNSS nodes (e.g., four or more satellites) and solve various equations to determine a corresponding GNSS location (e.g., spatial coordinates). The GNSS receiver also implements a clock that is generally less stable and accurate than the atomic clock of the GNSS node, and the GNSS receiver may use the measured GNSS signals to determine a deviation of the GNSS receiver from real time (e.g., a deviation of the GNSS receiver clock from the GNSS node time). In some embodiments, Positioning circuit XS45 may include a Micro-Technology for Positioning, Navigation, and Timing (Micro-PNT) IC that uses a master Timing clock to perform position tracking/estimation without GNSS assistance.

The GNSS receiver may measure the time of arrival (ToA) of GNSS signals from multiple GNSS nodes according to its own clock. The GNSS receiver may determine a time of flight (ToF) value for each received GNSS signal based on ToA and ToT, and may then determine a three-dimensional (3D) position and clock bias based on the ToF. The 3D location may then be converted to latitude, longitude, and altitude. The positioning circuit XS45 may provide data to the application circuit XS05, which may include one or more of location data or time data. The application circuit XS05 may use the time data to operate in synchronization with other radio base stations (e.g. RAN nodes XQ11, XQ12, XR11, etc.).

The components shown in fig. 11 may communicate with each other using interface circuitry. As used herein, the term "interface circuit" may refer to, be part of, or include a circuit that supports the exchange of information between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces, such as a bus, an input/output (I/O) interface, a peripheral component interface, a network interface card, and so forth. Any suitable bus technology may be used in various implementations, which may include any number of technologies, including Industry Standard Architecture (ISA), Extended ISA (EISA), Peripheral Component Interconnect (PCI), PCI extended PCI, PCI express (PCIe), or any number of other technologies. The bus may be a dedicated bus, such as used in SoC-based systems. Other bus systems may be included, such as an I2C interface, an SPI interface, a point-to-point interface, and a power bus, among others.

Fig. 12 illustrates an example of a platform XT00 (or "device XT 00"), in accordance with various embodiments. In embodiments, computer platform XT00 may be suitable for use as UE XQ01, XQ02, XR01, application server XQ30, and/or any other element/device discussed herein. The platform XT00 may comprise any combination of the components shown in the examples. The components of the platform XT00 may be implemented as an Integrated Circuit (IC), a portion thereof, discrete electronic devices or other modules adapted in the computer platform XT00, logic, hardware, software, firmware, or a combination thereof, or as components otherwise contained within the chassis of a larger system. The block diagram of fig. XT1 is intended to illustrate a high-level view of the components of computer platform XT 00. However, in other implementations, some of the components shown may be omitted, additional components may be present, and a different arrangement of the components shown may occur.

The application circuit XT05 may include circuits such as (but not limited to) the following: a single-core or multi-core processor and one or more of: cache memory, Low Dropout (LDO) regulator, interrupt controller, serial interface such as Serial Peripheral Interface (SPI), inter-integrated circuit (I2C), or universal programmable serial interface circuit, Real Time Clock (RTC), timer-counters including interval and watchdog timers, universal input-output (IO), memory card controller such as secure digital/multimedia card (SD/MMC), Universal Serial Bus (USB) interface, Mobile Industry Processor Interface (MIPI) interface, and Joint Test Access Group (JTAG) test access port. The processor(s) may include any combination of general-purpose processors and/or special-purpose processors (e.g., graphics processors, application processors, etc.). The processor (or core) may be coupled with or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the platform XT 00. In some embodiments, the processor applying circuitry XS05/XT05 may process IP data packets received from the EPC or the 5 GC.

The application circuit XT05 may be or may include a microprocessor, multi-core processor, multi-threaded processor, ultra-low voltage processor, embedded processor, or other known processing element. In one example, applying circuit XT05 can include basing onArchitecture Core^TMProcessors of, e.g. Quark^TM、Atom^TMI3, i5, i7 or an MCU class processor, or may be from Santa Clara, CalifAdditional such processors available from companies. The processor applying circuit XT05 may also be one or more of the following: (one or more) AMDA processor or APU; fromCompany's A5-A9 processor(s), fromSnapdagon(s) of technical company^TMProcessor, Texas Instrument Open Multimedia Applications Platform(s) (OMAP)^TMA processor; MIPS-based designs from MIPS technologies corporation; an ARM-based design licensed from ARM holdings limited; and so on. In some implementations, the application circuit XT05 can be part of a system-on-a-chip (SoC) in which the application circuit XT05 and other components are formed as a single integrated circuit, or a single package, e.g., fromCompany Edison^TMOr Galileo^TMAnd (6) an SoC board.

Additionally or alternatively, the application circuit XT05 may include circuits such as (but not limited to) the following: one or more Field Programmable Devices (FPDs), such as FPGAs and the like; programmable Logic Devices (PLDs), such as complex PLDs (cplds), high capacity PLDs (hcplds), and the like; ASICs, such as structured ASICs and the like; programmable soc (psoc); and so on. In such embodiments, the circuitry applying circuit XT05 may comprise a logic block or logic architecture, including other interconnected resources, that may be programmed to perform various functions, such as the processes, methods, functions, etc. of the various embodiments discussed herein. In such embodiments, the circuitry applying the circuit XT05 may include storage units (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., Static Random Access Memory (SRAM), antifuse, etc.) for storing logic blocks, logic architectures, data, etc. in a lookup table (LUT), and so forth.

Baseband circuit XT10 may be implemented, for example, as a solder-in substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits. Although not shown, baseband circuit XT10 may include one or more digital baseband systems that may be coupled to a CPU subsystem, an audio subsystem, and an interface subsystem via an interconnection subsystem. The digital baseband subsystem may also be coupled to the digital baseband interface and the mixed signal baseband subsystem via additional interconnect subsystems. Each interconnection subsystem may include a bus system, a point-to-point connection, a Network On Chip (NOC) fabric, and/or some other suitable bus or interconnection technology, such as those discussed herein. The audio subsystem may include digital signal processing circuitry, buffer memory, program memory, voice processing accelerator circuitry, data converter circuitry such as analog-to-digital and digital-to-analog converter circuitry, analog circuitry including one or more amplifiers and filters, and/or other similar components. In an aspect of the disclosure, baseband circuitry XT10 may include protocol processing circuitry having one or more instances of control circuitry (not shown) to provide control functions for digital baseband circuitry and/or radio frequency circuitry (e.g., radio front end module XT 15).

A Radio Front End Module (RFEM) XT15 may include a millimeter wave RFEM and one or more sub-millimeter wave Radio Frequency Integrated Circuits (RFICs). In some implementations, the one or more sub-millimeter wave RFICs may be physically separate from the millimeter wave RFEM. The RFIC may include a connection to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In an alternative implementation, both millimeter wave and sub-millimeter wave radio functions may be implemented in the same physical radio front end module XT 15. RFEM XT15 may include both millimeter wave and submillimeter wave antennas.

Memory circuit XT20 may comprise any number and type of memory devices for providing a given amount of system memory. As an example, memory circuit XT20 may include one or more of the following: easy to useVolatile memory including Random Access Memory (RAM), Dynamic RAM (DRAM), and/or Synchronous Dynamic RAM (SDRAM); and non-volatile memory (NVM), including high speed electrically erasable memory (often referred to as flash memory), phase change random access memory (PRAM), Magnetoresistive Random Access Memory (MRAM), and the like. Memory circuit XT20 may be developed in accordance with Joint Electron Devices Engineering Council (JEDEC) based Low Power Double Data Rate (LPDDR) designs such as LPDDR2, LPDDR3, LPDDR4, and the like. The memory circuit XT20 may be implemented as one or more of a solder-in package integrated circuit, a Single Die Package (SDP), a Dual Die Package (DDP) or quad die package (Q17P), a socket memory module, a Dual Inline Memory Module (DIMM) including a micro DIMM or a MiniDIMM, and/or soldered to a motherboard via a Ball Grid Array (BGA). In a low power implementation, memory circuit XT20 may be an on-chip memory or register associated with application circuit XT 05. To provide persistent storage for information such as data, applications, operating systems, and the like, memory circuit XT20 may include one or more mass storage devices, which may include Solid State Disk Drives (SSDDs), Hard Disk Drives (HDDs), micro HDDs, resistance change memories, phase change memories, holographic or chemical memories, among others. For example, computer platform XT00 may include a XT fromAnda three-dimensional (3D) cross point (XPOINT) memory.

Removable memory circuit XT23 may include devices, circuitry, enclosures/housings, ports or receptacles for coupling portable data storage devices with platform XT00, among others. These portable data storage devices may be used for mass storage purposes and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, microSD cards, xD picture cards, etc.), as well as USB flash drives, optical disks, external HDDs, and the like.

The platform XT00 may also include interface circuitry (not shown) for connecting external devices with the platform XT 00. External devices connected to platform XT00 via interface circuitry may include sensors XT21 such as accelerometers, level sensors, flow sensors, temperature sensors, pressure sensors, barometric pressure sensors, and the like. Interface circuitry may be used to connect platform XT00 to an electro-mechanical component (EMC) XT22, EMC XT22 may allow platform XT00 to change its state, position and/or orientation, or to move or control a mechanism or system. EMC XT22 may include one or more power switches, relays including electromechanical relays (EMRs) and/or Solid State Relays (SSRs), actuators (e.g., valve actuators, etc.), audible sound generators, visual alert devices, motors (e.g., dc motors, stepper motors, etc.), wheels, propellers, claws, clamps, hooks, and/or other similar electromechanical components. In embodiments, the platform XT00 may be configured to operate one or more EMC XT22 based on one or more captured events and/or instructions or control signals received from a service provider and/or various clients.

In some implementations, interface circuitry can connect platform XT00 with positioning circuitry XT45, positioning circuitry XT45 can be the same as or similar to positioning circuitry XS45 discussed with reference to fig. 11.

In some implementations, interface circuitry can connect platform XT00 with Near Field Communication (NFC) circuitry XT40, and NFC circuitry XT40 can include an NFC controller coupled with antenna elements and processing devices. NFC circuit XT40 may be configured to read an electronic tag and/or connect with another NFC-enabled device.

Driver circuit XT46 may include software and hardware elements that operate to control specific devices embedded in platform XT00, attached to platform XT00, or otherwise communicatively coupled with platform XT 00. The driver circuit XT46 may include individual drivers that allow other components of the platform XT00 to interact with or control various input/output (I/O) devices that may be present within the platform XT00 or connected to the platform XT 00. For example, driver circuit XT46 may include display drivers to control and allow access to a display device, touch screen drivers to control and allow access to the touch screen interface of platform XT00, sensor drivers to obtain sensor readings of sensor XT21 and control and allow access to sensor XT21, EMC drivers to obtain actuator positions of EMC XT22 and/or control and allow access to EMC XT22, camera drivers to control and allow access to embedded image capture devices, and audio drivers to control and allow access to one or more audio devices.

A Power Management Integrated Circuit (PMIC) XT25 (also referred to as "power management circuit XT 25") may manage power provided to various components of platform XT 00. Specifically, for baseband circuit XT10, PMIC XT25 may control power supply selection, voltage scaling, battery charging, or DC-to-DC conversion. PMIC XT25 can often be included when platform XT00 can be powered by battery XT30, such as when the device is included in UEXQ01, XQ02, XR 01.

In some embodiments, PMIC XT25 may control or otherwise be part of various power saving mechanisms of platform XT 00. For example, if platform XT00 is in RRC _ Connected state, which is still Connected to the RAN node because it is expected to receive traffic very soon, it may enter a state called Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, platform XT00 may be powered down for brief time intervals and thereby save power. If there is no data traffic activity for a longer period of time, the platform XT00 may transition off to the RRC _ Idle state where it is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. Platform XT00 enters a very low power state and it performs a page in which it again periodically wakes up to listen to the network and then powers down again. Platform XT00 may not receive data in this state, and in order to receive data it must transition back to the RRC Connected state. The additional power saving mode may allow the device to be unavailable to the network for periods longer than the paging interval (ranging from seconds to hours). During this time, the device is completely inaccessible to the network and can be completely powered down. Any data sent during this time is subject to a large delay and it is assumed that the delay is acceptable.

Battery XT30 may power platform XT00, although in some examples platform XT00 may be installed deployed in a fixed location and may have a power supply source coupled to the power transmission network. Battery XT30 may be a lithium ion battery, a metal air battery such as a zinc air battery, an aluminum air battery, a lithium air battery, or the like. In some implementations, such as in a V2X application, battery XT30 may be a typical lead-acid automotive battery.

In some implementations, Battery XT30 can be a "smart Battery" that includes or is coupled to a Battery Management System (BMS) or Battery monitoring integrated circuit. The BMS may be included in the platform XT00 to track the state of charge (SoCh) of the battery XT 30. The BMS may be used to monitor other parameters of battery XT30 to provide failure predictions, such as the state of health (SoH) and functional state (SoF) of battery XT 30. The BMS can communicate information of battery XT30 to the application circuit XT05 or other components of the platform XT 00. The BMS can also include an analog-to-digital (ADC) converter that allows the application circuit XT05 to directly monitor the voltage of battery XT30 or the current flowing from battery XT 30. The battery parameters may be used to determine actions that the platform XT00 may perform, such as transmit frequency, network operation, sense frequency, and the like.

A power block or other power supply coupled to the power transmission network may be coupled to the BMS to charge battery XT 30. In some examples, the power block XQ28 may be replaced with a wireless power receiver to obtain power wirelessly, such as through a loop antenna in the computer platform XT 00. In these examples, a wireless battery charging circuit may be included in the BMS. The particular charging circuit selected may depend on the size of battery XT30 and thus on the current required. Charging may be performed using the Airfuel standard promulgated by the international Wireless charging industry Consortium (Airfuel Alliance), the Qi Wireless charging standard promulgated by the Wireless Power Consortium (Wireless Power Consortium), or the Rezence charging standard promulgated by the Wireless Power Consortium (Alliance for Wireless Power), among others.

Although not shown, the components of platform XT00 may communicate with each other using appropriate bus technology, which may include any number of technologies, including Industry Standard Architecture (ISA), extended ISA (eisa), Peripheral Component Interconnect (PCI), extended Peripheral Component Interconnect (PCI), PCI express (pcie), Time-triggered protocol (TTP) systems, or FlexRay systems, or any number of other technologies. The bus may be a dedicated bus, such as used in SoC-based systems. Other bus systems may be included, such as an I2C interface, an SPI interface, a point-to-point interface, and a power bus, among others.

Fig. 13 illustrates example components of baseband circuitry XS10/XT10 and radio front-end modules (RFEM) XS15/XT15, in accordance with some embodiments. As shown, RFEM XS15/XT15 may include at least Radio Frequency (RF) circuit XT06, Front End Module (FEM) circuit XT08, one or more antennas XT10 coupled together as shown.

Baseband circuitry XS10/XT10 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. Baseband circuits XS10/XT10 may include one or more baseband processors or control logic to process baseband signals received from the receive signal path of RF circuit XT06 and generate baseband signals for the transmit signal path of RF circuit XT 06. The baseband processing circuits XS10/XT10 may interface with application circuits XS05/XT05 to generate and process baseband signals and control the operation of the RF circuits XT 06. For example, in some embodiments, baseband circuitry XS10/XT10 may include third generation (3G) baseband processor XT04A, fourth generation (4G) baseband processor XT04B, fifth generation (5G) baseband processor XT04C, or other baseband processor(s) XT04D for other existing generations, generations in development, or generations to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuits XS10/XT10 (e.g., one or more of the baseband processors XT 04A-D) may handle various radio control functions that enable communication with one or more radio networks via the RF circuits XT 06. In other embodiments, some or all of the functionality of the baseband processor XT04A-D may be included in modules stored in memory XT04G and executed via a Central Processing Unit (CPU) XT 04E. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency offset, and the like. In some embodiments, the modulation/demodulation circuitry of baseband circuitry XS10/XT10 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments, the encoding/decoding circuitry of baseband circuitry XS10/XT10 may include convolutional, tail-biting convolutional, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functions are not limited to these examples, and other suitable functions may be included in other embodiments.

In some embodiments, the baseband circuitry XS10/XT10 may include one or more audio Digital Signal Processors (DSPs) XT 04F. The audio DSP XT 04(s) 04F may include elements for compression/decompression and echo cancellation, and may include other suitable processing elements in other embodiments. The components of the baseband circuitry may be combined as appropriate in a single chip, in a single chipset, or in some embodiments arranged on the same circuit board. In some embodiments, some or all of the constituent components of the baseband circuits XS10/XT10 and the application circuits XS05/XT05 may be implemented together, for example, on a system on a chip (SOC).

In some embodiments, baseband circuitry XS10/XT10 may provide communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry XS10/XT10 may support communication with evolved universal terrestrial radio access network (E-UTRAN) or other Wireless Metropolitan Area Network (WMAN), Wireless Local Area Network (WLAN), Wireless Personal Area Network (WPAN). Embodiments in which the baseband circuitry XS10/XT10 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

RF circuit XT06 may enable communication with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various embodiments, RF circuit XT06 may include switches, filters, amplifiers, and the like to facilitate communication with a wireless network. RF circuitry XT06 may include a receive signal path that may include circuitry to down-convert RF signals received from FEM circuitry XT08 and provide baseband signals to baseband circuitry XS10/XT 10. RF circuit XT06 may also include a transmit signal path that may include circuitry to up-convert baseband signals provided by baseband circuits XS10/XT10 and provide an RF output signal to FEM circuit XT08 for transmission.

In some embodiments, the receive signal path of RF circuit XT06 may include mixer circuit XT06a, amplifier circuit XT06b, and filter circuit XT06 c. In some embodiments, the transmit signal path of RF circuit XT06 may include filter circuit XT06c and mixer circuit XT06 a. RF circuit XT06 may also include a synthesizer circuit XT06d for synthesizing frequencies for use by mixer circuit XT06a of the receive signal path and the transmit signal path. In some embodiments, mixer circuit XT06a of the receive signal path may be configured to down-convert RF signals received from FEM circuit XT08 based on the synthesized frequency provided by synthesizer circuit XT06 d. Amplifier circuit XT06b may be configured to amplify the down-converted signal and filter circuit XT06c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signals may be provided to baseband circuitry XS10/XT10 for further processing. In some embodiments, the output baseband signal may be a zero frequency baseband signal, although this is not a necessary requirement. In some embodiments, mixer circuit XT06a of the receive signal path may comprise a passive mixer, although the scope of the embodiments is not limited in this respect.

In some embodiments, mixer circuit XT06a of the transmit signal path may be configured to upconvert an input baseband signal based on a synthesized frequency provided by synthesizer circuit XT06d to generate an RF output signal for FEM circuit XT 08. The baseband signals may be provided by baseband circuits XS10/XT10 and may be filtered by filter circuit XT06 c.

In some embodiments, mixer circuit XT06a of the receive signal path and mixer circuit XT06a of the transmit signal path may comprise two or more mixers and may be arranged for quadrature down-conversion and up-conversion, respectively. In some embodiments, mixer circuit XT06a of the receive signal path and mixer circuit XT06a of the transmit signal path may comprise two or more mixers and may be arranged for image rejection (e.g., hartley image rejection). In some embodiments, mixer circuit XT06a and mixer circuit XT06a of the receive signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, mixer circuit XT06a of the receive signal path and mixer circuit XT06a of the transmit signal path may be configured for superheterodyne operation.

In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, RF circuit XT06 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits and baseband circuits XS10/XT10 may include digital baseband interfaces to communicate with RF circuit XT 06.

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

In some embodiments, synthesizer circuit XT06d may be a fractional-N synthesizer or a fractional-N/N +1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuit XT06d may be an incremental sum synthesizer, a frequency multiplier, or a synthesizer including a phase locked loop with a frequency divider.

The synthesizer circuit XT06d can be configured to synthesize an output frequency based on a frequency input and a divider control input for use by mixer circuit XT06a of RF circuit XT 06. In some embodiments, synthesizer circuit XT06d may be a fractional-N/N +1 type synthesizer.

In some embodiments, the frequency input may be provided by a Voltage Controlled Oscillator (VCO), although this is not a necessary requirement. The divider control inputs may be provided by baseband circuits XS10/XT10 or application processors XS05/XT05, depending on the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a look-up table based on the channel indicated by the application processor XS05/XT 05.

Synthesizer circuit XT06d of RF circuit XT06 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the divider may be a Dual Modulus Divider (DMD) and the phase accumulator may be a Digital Phase Accumulator (DPA). In some embodiments, the DMD may be configured to divide an input signal by N or N +1 (e.g., based on a carry out) to provide a fractional divide ratio. In some example embodiments, a DLL may include a set of cascaded tunable delay elements, a phase detector, a charge pump, and a D-type flip-flop. In these embodiments, the delay elements may be configured to decompose the VCO period into Nd equal phase groups, where Nd is the number of delay elements in the delay line. Thus, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

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

FEM circuitry XT08 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas XT10, amplify the received signals, and provide amplified versions of the received signals to RF circuitry XT06 for further processing. FEM circuit XT08 may also include a transmit signal path that may include circuitry configured to amplify signals provided for transmission by RF circuit XT06 for transmission by one or more of one or more antennas XT 10. In various embodiments, amplification through the transmit or receive path may be done in RF circuit XT06 only, FEM XT08 only, or both RF circuits XT06 and FEM XT 08.

In some embodiments, FEM circuit XT08 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include an LNA to amplify a received RF signal and provide the amplified receive RF signal as an output (e.g., to RF circuit XT 06). The transmit signal path of FEM circuit XT08 may include a Power Amplifier (PA) to amplify an incoming RF signal (e.g., provided by RF circuit XT06) and one or more filters to generate the RF signal for subsequent transmission (e.g., by one or more of one or more antennas XT 10).

Processors of the application circuits XS05/XT05 and processors of the baseband circuits XS10/XT10 may be used to execute elements of one or more instances of a protocol stack. For example, the processors of baseband circuits XS10/XT10, alone or in combination, may be used to perform layer 3, layer 2, or layer 1 functions, while the processors of baseband circuits XS10/XT10 may utilize data (e.g., packet data) received from these layers and further perform layer 4 functions (e.g., Transmission Communication Protocol (TCP) and User Datagram Protocol (UDP) layers). As referred to herein, layer 3 may include a Radio Resource Control (RRC) layer, which is described in more detail below. As referred to herein, layer 2 may include a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, and a Packet Data Convergence Protocol (PDCP) layer, which are described in more detail below. Layer 1, as referred to herein, may comprise the Physical (PHY) layer of the UE/RAN node, which is described in more detail below.

Fig. 14 illustrates example interfaces of baseband circuitry, in accordance with some embodiments. As described above, baseband circuitry XS10/XT10 of diagram XS-diagram XT1 may include processors XT04A-XT04E and memory XT04G utilized by the processors. Each of processors XT04A-XT04E may include a memory interface, XU04A-XU04E, respectively, to send/receive data to/from memory XT 04G.

The baseband circuitry XS10/XT10 may also include one or more interfaces to communicatively couple to other circuitry/devices, such as a memory interface XU12 (e.g., an interface to transmit/receive data to/from memory external to the baseband circuitry XS10/XT 10), an application circuitry interface XU14 (e.g., an interface to transmit/receive data to/from the application circuitry XS05/XT05 of fig. XS-XT 1), an RF circuitry interface XU16 (e.g., an interface to transmit/receive data to/from the RF circuitry XT06 of fig. XT 2), a wireless hardware connectivity interface XU18 (e.g., a Near Field Communication (NFC) component, a wireless hardware connectivity interface XU18,Component (e.g. low energy consumption))、Interfaces for components and other communication components to send/receive data) and a power management interface XU20 (e.g., an interface to send/receive power or control signals to/from PMIC XT 25).

Figure 15 is an illustration of a control plane protocol stack according to some embodiments. In this embodiment, the control plane XV00 is shown as a communication protocol stack between UE XQ01 (or UE XQ02), RAN node XQ11 (or RAN node XQ12), and MME XQ 21.

The PHY layer XV01 may send or receive information over one or more air interfaces for use by the MAC layer XV 02. The PHY layer XV01 may also perform link adaptive or Adaptive Modulation and Coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers (e.g., the RRC layer XV 05). PHY layer XV01 may also perform error detection on transport channels, Forward Error Correction (FEC) encoding/decoding of transport channels, modulation/demodulation of physical channels, interleaving, rate matching, mapping onto physical channels, and Multiple Input Multiple Output (MIMO) antenna processing.

The MAC layer XV02 may perform mapping between logical channels and transport channels, multiplexing of MAC Service Data Units (SDUs) from one or more logical channels onto Transport Blocks (TBs) for delivery to the PHY via the transport channels, demultiplexing of MAC SDUs from Transport Blocks (TBs) delivered from the PHY via the transport channels onto one or more logical channels, multiplexing of MAC SDUs onto the TBs, scheduling information reporting, error correction by hybrid automatic repeat request (HARQ), and logical channel prioritization.

The RLC layer XV03 may operate in a variety of operating modes, including: transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC layer XV03 may perform transmission of upper layer Protocol Data Units (PDUs), error correction by automatic repeat request (ARQ) for AM data transmission, and concatenation, segmentation, and reassembly of RLC SDUs for UM and AM data transmission. The RLC layer XV03 may also perform re-segmentation of RLC data PDUs for AM data transfer, reordering RLC data PDUs for UM and AM data transfer, detecting duplicate data for UM and AM data transfer, discarding RLC SDUs for UM and AM data, detecting protocol errors for AM data transfer, and performing RLC re-establishment.

The PDCP layer XV04 may perform header compression and decompression of IP data, maintain PDCP Sequence Number (SN), perform in-order delivery of upper layer PDUs at lower layer re-establishment, eliminate duplication of lower layer SDUs at lower layer re-establishment for radio bearers mapped onto the RLC AM, cipher and decipher control plane data, perform integrity protection and integrity verification of control plane data, timer-based dropping of control data, and perform security operations (e.g., ciphering, deciphering, integrity protection, integrity verification, etc.).

The main services and functions of the RRC layer XV05 may include broadcasting of System Information (e.g., included in a Master Information Block (MIB) or a System Information Block (SIB) related to a non-access stratum (NAS)), broadcasting of System Information related to an Access Stratum (AS), paging, establishment, maintenance and release of RRC connections between the UE and the E-UTRAN (e.g., RRC connection paging, RRC connection establishment, RRC connection modification and RRC connection release), establishment, configuration, maintenance and release of point-to-point radio bearers, security functions including key management, inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting. The MIB and SIBs may include one or more Information Elements (IEs), each of which may include an individual data field or data structure.

The UE XQ01 and the RAN node XQ11 may utilize a Uu interface (e.g., LTE-Uu interface) to exchange control plane data via a protocol stack including a PHY layer XV01, a MAC layer XV02, an RLC layer XV03, a PDCP layer XV04, and an RRC layer XV 05.

The non-access stratum (NAS) protocol XV06 forms the highest level of the control plane between UE XQ01 and MME XQ 21. The NAS protocol XV06 supports mobility and session management procedures for UE XQ01 to establish and maintain IP connectivity between UE XQ01 and P-GW XQ 23.

The S1 application protocol (S1-AP) layer XV15 may support the functionality of the S1 interface XQ13 and include Elementary Procedures (EP). The EP is the unit of interaction between the RAN node XQ11 and CN XQ 20. The S1-AP layer services may include two groups: UE-associated services and non-UE-associated services. These services perform functions that include, but are not limited to: E-UTRAN Radio Access Bearer (E-RAB) Management, UE capability indication, mobility, NAS signaling, RAN Information Management (RIM), and configuration transfer.

The Stream Control Transmission Protocol (SCTP) layer (alternatively referred to as the SCTP/IP layer) XV14 may ensure reliable delivery of signaling messages between the RAN node XQ11 and the MME XQ21 based in part on the IP Protocol supported by the IP layer XV 13. The L2 layer XV12 and the L1 layer XV11 may refer to communication links (e.g., wired or wireless) used by the RAN node and MME to exchange information.

The RAN nodes XQ11 and MME XQ21 may utilize the S1-MME interface to exchange control plane data via a protocol stack including L1 layer XV11, L2 layer XV12, IP layer XV13, SCTP layer XV14, and S1-AP layer XV 15.

Fig. 16 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein, according to some example embodiments. In particular, the diagram XZ shows a diagrammatic representation of hardware resources XZ00, hardware resources XZ00 including one or more processors (or processor cores) XZ10, one or more memory/storage devices XZ20, and one or more communication resources XZ30, each of which may be communicatively coupled via a bus XZ 40. As used herein, the terms "computing resource," "hardware resource," and the like may refer to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as a computer device, a mechanical device, a memory space, processor/CPU time and/or processor/CPU usage, processor and accelerator load, hardware time or usage, power supply, input/output operations, ports or network sockets, channel/link assignments, throughput, memory usage, storage, networks, databases, and applications, and the like. For embodiments utilizing node virtualization (e.g., NFV), a hypervisor (hypervisor) XZ02 may be executed to provide an execution environment for one or more network slices/subslices utilizing hardware resources XZ 00. "virtualized resources" may refer to computing, storage, and/or network resources provided by a virtualization infrastructure to applications, devices, systems, and so forth.

The processor XZ10 (e.g., a Central Processing Unit (CPU), a Reduced Instruction Set Computing (RISC) processor, a Complex Instruction Set Computing (CISC) processor, a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP) (e.g., a baseband processor), an Application Specific Integrated Circuit (ASIC), a Radio Frequency Integrated Circuit (RFIC), another processor, or any suitable combination of these) may include, for example, the processor XZ12 and the processor XZ 14.

The memory/storage device XZ20 may comprise main memory, disk storage, or any suitable combination of these. The memory/storage XZ20 may include, but is not limited to, any type of volatile or non-volatile memory, such as Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid state storage, and the like.

The communication resources XZ30 may include interconnect or network interface components or other suitable devices to communicate with one or more peripheral devices XZ04 or one or more databases XZ06 via a network XZ 08. For example, communication resource XZ30 may include a wired communication component (e.g., for coupling via a Universal Serial Bus (USB)), a cellular communication component, an NFC component, a wireless communication component,component (e.g. low energy consumption))，Components and other communication components. As used herein, the term "network resource" or "communication resource" may refer to a computing resource accessible by a computer device via a communication network. The term "system resource" may refer to any kind of shared entity that provides a service, and may include computing and/or network resources. A system resource may be considered a collection of coherent functions, network data objects, or services accessible through a server, where such system resource exists on a single host or multiple hosts and is clearly identifiable.

The instructions XZ50 may include software, a program, an application, an applet, an app, or other executable code for causing at least any one of the processors XZ10 to perform any one or more of the methods discussed herein. The instruction XZ50 may reside, completely or partially, within at least one of the processors XZ10 (e.g., within a cache memory of the processor), within the memory/storage XZ20, or any suitable combination of these. Further, any portion of the instructions XZ50 may be transferred to the hardware resources XZ00 from any combination of the peripheral XZ04 or the database XZ 06. Thus, the memory of processor XZ10, memory/storage device XZ20, peripheral XZ04, and database XZ06 are examples of computer-readable and machine-readable media.

For one or more embodiments, at least one of the components set forth in one or more of the foregoing figures may be configured to perform one or more of the operations, techniques, processes, and/or methods set forth in the example section below. For example, the baseband circuitry described above in connection with one or more of the foregoing 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., described above in connection with one or more of the preceding figures, can be configured to operate in accordance with one or more of the examples set forth below in the example section.

Examples of the invention

Example 1 may include a method comprising: transmitting, by a base station, an indication of a first set of parameters related to a control channel in a first physical channel transmission; and transmitting, by the base station, an indication of a second set of parameters related to the control channel in a control channel transmission using the first set of parameters.

Example 2 may include the method of example 1, wherein the first physical channel transmission is a Physical Broadcast Channel (PBCH) transmission.

Example 3 may include the method of example 2, wherein the PBCH transmission is a New Radio (NR) -PBCH transmission.

Example 4 may include the method of example 1, wherein the control channel transmission is a Physical Downlink Control Channel (PDCCH) transmission.

Example 5 may include the method of example 4, wherein the PDCCH transmission is a New Radio (NR) -PDCCH transmission.

Example 6 may include the method of example 4, wherein the control channel transmission involves a Physical Downlink Shared Channel (PDSCH) transmission including Remaining Minimal System Information (RMSI) elements.

Example 7 may include the method of any of examples 1-6, wherein the first set of parameters relates to a first set of timing parameters that may be used by a User Equipment (UE) to monitor for the control channel transmission.

Example 8 may include the method of example 7, wherein the second set of parameters relates to a second set of timing information usable by a User Equipment (UE) to monitor for subsequent control channel transmissions.

Example 9 may include the method of any of examples 1-6, wherein the first set of parameters is a first subset of control channel resource set (CORESET) parameters.

Example 10 may include the method of example 9, wherein the second set of parameters is a second subset of CORESET parameters that is different from the first subset of CORESET parameters.

Example 11 may include one or more computer-readable media comprising instructions that, when executed by one or more processors of a base station, cause the base station to: transmitting an indication of a first set of parameters related to a control channel in a first physical channel transmission; and transmitting, by the base station, an indication of a second set of parameters related to the control channel in a control channel transmission using the first set of parameters.

Example 12 may include the one or more computer-readable media of example 11, wherein the first physical channel transmission is a Physical Broadcast Channel (PBCH) transmission.

Example 13 may include the one or more computer-readable media of example 12, wherein the PBCH transmission is a New Radio (NR) -PBCH transmission.

Example 14 may include the one or more computer-readable media of example 11, wherein the control channel transmission is a Physical Downlink Control Channel (PDCCH) transmission.

Example 15 may include the one or more computer-readable media of example 14, wherein the PDCCH transmission is a New Radio (NR) -PDCCH transmission.

Example 16 may include the one or more computer-readable media of example 14, wherein the control channel transmission relates to a Physical Downlink Shared Channel (PDSCH) transmission including Remaining Minimal System Information (RMSI) elements.

Example 17 may include the one or more computer-readable media of any of examples 11-17, wherein the first set of parameters relates to a first set of timing parameters that may be used by a User Equipment (UE) to monitor for the control channel transmission.

Example 18 may include the one or more computer-readable media of example 17, wherein the second set of parameters relates to a second set of timing information usable by a User Equipment (UE) to monitor for subsequent control channel transmissions.

Example 19 may include the one or more computer-readable media of any of examples 11-17, wherein the first set of parameters is a first subset of control channel resource set (CORESET) parameters.

Example 20 may include the one or more computer-readable media of example 19, wherein the second set of parameters is a second subset of CORESET parameters that is different from the first subset of CORESET parameters.

Example 21 may include a base station comprising: means for transmitting an indication of a first set of parameters related to a control channel in a first physical channel transmission; and means for transmitting, by the base station, an indication of a second set of parameters related to the control channel in a control channel transmission using the first set of parameters.

Example 22 may include the base station of example 21, wherein the first physical channel transmission is a Physical Broadcast Channel (PBCH) transmission.

Example 23 may include the base station of example 22, wherein the PBCH transmission is a New Radio (NR) -PBCH transmission.

Example 24 may include the base station of example 21, wherein the control channel transmission is a Physical Downlink Control Channel (PDCCH) transmission.

Example 25 may include the base station of example 24, wherein the PDCCH transmission is a New Radio (NR) -PDCCH transmission.

Example 26 may include the base station of example 24, wherein the control channel transmission relates to a Physical Downlink Shared Channel (PDSCH) transmission including Remaining Minimal System Information (RMSI) elements.

Example 27 may include the base station of any of examples 21-26, wherein the first set of parameters relates to a first set of timing parameters that may be used by a User Equipment (UE) to monitor for the control channel transmission.

Example 28 may include the base station of example 27, wherein the second set of parameters relates to a second set of timing information usable by a User Equipment (UE) to monitor for subsequent control channel transmissions.

Example 29 may include the base station of any of examples 21-26, wherein the first set of parameters is a first subset of control channel resource set (CORESET) parameters.

Example 30 may include the base station of example 29, wherein the second set of parameters is a second subset of CORESET parameters that is different from the first subset of CORESET parameters.

Example 31 may include a base station comprising: a processor; and one or more computer-readable media communicatively coupled with the processor, wherein the one or more computer-readable media comprise instructions that, when executed by the processor, cause the processor to: transmitting an indication of a first set of parameters related to a control channel in a first physical channel transmission; and transmitting, by the base station, an indication of a second set of parameters related to the control channel in a control channel transmission using the first set of parameters.

Example 32 may include the base station of example 31, wherein the first physical channel transmission is a Physical Broadcast Channel (PBCH) transmission.

Example 33 may include the base station of example 32, wherein the PBCH transmission is a New Radio (NR) -PBCH transmission.

Example 34 may include the base station of example 31, wherein the control channel transmission is a Physical Downlink Control Channel (PDCCH) transmission.

Example 35 may include the base station of example 34, wherein the PDCCH transmission is a New Radio (NR) -PDCCH transmission.

Example 36 may include the base station of example 34, wherein the control channel transmission relates to a Physical Downlink Shared Channel (PDSCH) transmission including Remaining Minimal System Information (RMSI) elements.

Example 37 may include the base station of any of examples 31-36, wherein the first set of parameters relates to a first set of timing parameters that may be used by a User Equipment (UE) to monitor for the control channel transmission.

Example 38 may include the base station of example 37, wherein the second set of parameters relates to a second set of timing information usable by a User Equipment (UE) to monitor for subsequent control channel transmissions.

Example 39 may include the base station of any of examples 31-36, wherein the first set of parameters is a first subset of control channel resource set (CORESET) parameters.

Example 40 may include the base station of example 39, wherein the second set of parameters is a second subset of CORESET parameters that is different from the first subset of CORESET parameters.

Example 41 may include a method comprising: identifying, by a base station, a first parameter related to a Resource Element Group Bundle (REGB) of an interleaved Physical Downlink Control Channel (PDCCH) transmission, wherein the first parameter is selected from a first plurality of parameters; interleaving, by the base station, the REGB based on the first parameter to form a Control Channel Element (CCE); and transmitting, by the base station, the CCE in the PDCCH transmission.

Example 42 may include the method of example 41, wherein the REGB is a REGB transmitted by a set of control channel resources (CORESET).

Example 43 may include the method of example 41 or 42, wherein the first parameter relates to a number of stages of an interleaver that performs interleaving of the REGB.

Example 44 may include the method of example 43, further comprising: identifying, by the base station, a second parameter related to REGB of the PDCCH transmission, wherein the second parameter is selected from a second plurality of parameters; and interleaving, by the base station, the REGB based on the second parameter to form the CCE.

Example 45 may include the method of example 44, wherein the second parameter relates to a number of REGBs in the CCE for a stage of the interleaver.

Example 46 may include the method of example 44, wherein the second parameter is related to a number of rows of an interleaving matrix used by a stage of the interleaver.

Example 47 may include the method of example 44, wherein the second parameter relates to a number of columns of an interleaving matrix used by a stage of the interleaver.

Example 48 may include the method of example 44, wherein the second parameter relates to a column permutation pattern vector of a stage of the interleaver.

Example 49 may include the method of example 48, wherein the column permutation pattern vector is a function of a cell Identifier (ID), a Virtual Cell Identifier (VCID), or a user equipment identifier (UE ID).

Example 50 may include one or more computer-readable media comprising instructions that, when executed by one or more processors of a base station, cause the base station to: identifying a first parameter related to a Resource Element Group Bundle (REGB) of an interleaved Physical Downlink Control Channel (PDCCH) transmission, wherein the first parameter is selected from a first plurality of parameters; interleaving the REGB based on the first parameter to form a Control Channel Element (CCE); and transmitting the CCE in the PDCCH transmission.

Example 51 may include the one or more computer-readable media of example 50, wherein the REGB is a REGB of a control channel resource set (CORESET) transmission.

Example 52 may include the one or more computer-readable media of examples 50 or 51, wherein the first parameter is related to a number of stages of an interleaver that performs interleaving of the REGB.

Example 53 may include one or more computer-readable media as described in example 52, wherein the instructions are further to: identifying a second parameter related to a REGB of the PDCCH transmission, wherein the second parameter is selected from a second plurality of parameters; and interleaving the REGB based on the second parameter to form the CCE.

Example 54 may include the one or more computer-readable media of example 53, wherein the second parameter relates to a number of REGBs in the CCE for a stage of the interleaver.

Example 55 may include the one or more computer-readable media of example 53, wherein the second parameter is related to a number of rows of an interleaving matrix used by a stage of the interleaver.

Example 56 may include the one or more computer-readable media of example 53, wherein the second parameter is related to a number of columns of an interleaving matrix used by a stage of the interleaver.

Example 57 may include the one or more computer-readable media of example 53, wherein the second parameter relates to a column permutation pattern vector of a stage of the interleaver.

Example 58 may include the one or more computer-readable media of example 57, wherein the column permute pattern vector is a function of a cell Identifier (ID), a Virtual Cell Identifier (VCID), or a user equipment identifier (UE ID).

Example 59 may include a base station, comprising: means for identifying a first parameter related to a Resource Element Group Bundle (REGB) of interleaved Physical Downlink Control Channel (PDCCH) transmissions, wherein the first parameter is selected from a first plurality of parameters; means for interleaving the REGB based on the first parameter to form a Control Channel Element (CCE); and means for transmitting the CCE in the PDCCH transmission.

Example 60 may include the base station of example 59, wherein the REGB is a REGB of a control channel resource set (CORESET) transmission.

Example 61 may include the base station of example 59 or 60, wherein the first parameter relates to a number of stages of an interleaver that performs interleaving of the REGB.

Example 62 may include the base station of example 61, further comprising: means for identifying a second parameter related to REGB of the PDCCH transmission, wherein the second parameter is selected from a second plurality of parameters; and means for interleaving the REGB based on the second parameter to form the CCE.

Example 63 may include the base station of example 62, wherein the second parameter relates to a number of REGBs in the CCE for a phase of the interleaver.

Example 64 may include the base station of example 62, wherein the second parameter is related to a number of rows of an interleaving matrix used by a stage of the interleaver.

Example 65 may include the base station of example 62, wherein the second parameter relates to a number of columns of an interleaving matrix used by a stage of the interleaver.

Example 66 may include the base station of example 62, wherein the second parameter relates to a column permutation pattern vector of a stage of the interleaver.

Example 67 may include the base station of example 66, wherein the column permutation pattern vector is a function of a cell Identifier (ID), a Virtual Cell Identifier (VCID), or a user equipment identifier (UE ID).

Example 68 may include a base station, comprising: a processor; and one or more computer-readable media comprising instructions that, when executed by the processor, cause the base station to: identifying a first parameter related to a Resource Element Group Bundle (REGB) of an interleaved Physical Downlink Control Channel (PDCCH) transmission, wherein the first parameter is selected from a first plurality of parameters; interleaving the REGB based on the first parameter to form a Control Channel Element (CCE); and transmitting the CCE in the PDCCH transmission.

Example 69 may include the base station of example 68, wherein the REGB is a REGB transmitted by a set of control channel resources (CORESET).

Example 70 may include the base station of example 68 or 69, wherein the first parameter relates to a number of stages of an interleaver that performs interleaving of the REGB.

Example 71 may include the base station of example 70, wherein the instructions are further to: identifying a second parameter related to a REGB of the PDCCH transmission, wherein the second parameter is selected from a second plurality of parameters; and interleaving the REGB based on the second parameter to form the CCE.

Example 72 may include the base station of example 71, wherein the second parameter relates to a number of REGBs in the CCE for a phase of the interleaver.

Example 73 may include the base station of example 71, wherein the second parameter is related to a number of rows of an interleaving matrix used by a stage of the interleaver.

Example 74 may include the base station of example 71, wherein the second parameter relates to a number of columns of an interleaving matrix used by a stage of the interleaver.

Example 75 may include the base station of example 71, wherein the second parameter relates to a column permutation pattern vector of a stage of the interleaver.

Example 76 may include the base station of example 75, wherein the column permutation pattern vector is a function of a cell Identifier (ID), a Virtual Cell Identifier (VCID), or a user equipment identifier (UE ID).

Example 77 may include a method comprising: sending, by a base station, an indication of a first set of parameters related to a Physical Downlink Control Channel (PDCCH) transmission in a Physical Broadcast Channel (PBCH) transmission; identifying, by the base station, a first parameter related to a Resource Element Group Bundle (REGB) interleaving the PDCCH transmissions, wherein the first parameter is selected from a first plurality of parameters; interleaving, by the base station, the REGB based on the first parameter to form a Control Channel Element (CCE); and transmitting, by the base station, the CCE in the PDCCH transmission according to the first set of parameters related to the PDCCH transmission, wherein the CCE is related to an indication of a second set of parameters related to the PDCCH.

Example 78 may include the method of example 77, wherein the indication of the second set of parameters related to the PDCCH is a Remaining Minimum System Information (RMSI) transmission.

Example 79 may include the method of example 77, wherein the PBCH transmission is a New Radio (NR) -PBCH transmission.

Example 80 may include the method of example 77, wherein the PDCCH transmission is a New Radio (NR) -PDCCH transmission.

Example 81 may include the method of example 77, wherein the first set of parameters relates to a first set of timing parameters that may be used by a User Equipment (UE) to monitor the PDCCH transmission.

Example 82 may include the method of example 81, wherein the second set of parameters relates to a second set of timing information usable by a User Equipment (UE) to monitor for a subsequent PDCCH transmission.

Example 83 may include the method of example 77, wherein the first set of parameters is a first subset of control channel resource set (CORESET) parameters.

Example 84 may include the method of example 83, wherein the second set of parameters is a second subset of CORESET parameters that is different from the first subset of CORESET parameters.

Example 85 may include the method of example 77, wherein the REGB is a REGB transmitted by a set of control channel resources (CORESET).

Example 86 may include the method of any of examples 77-85, wherein the first parameter relates to a number of stages of an interleaver that performs interleaving of the REGB.

Example 87 may include the method of example 86, further comprising: identifying, by the base station, a second parameter related to REGB of the PDCCH transmission, wherein the second parameter is selected from a second plurality of parameters; and interleaving, by the base station, the REGB based on the second parameter to form the CCE.

Example 88 may include the method of example 87, wherein the second parameter relates to a number of REGBs in the CCE for a stage of the interleaver.

Example 89 may include the method of example 87, wherein the second parameter relates to a number of rows of an interleaving matrix used by a stage of the interleaver.

Example 90 may include the method of example 87, wherein the second parameter relates to a number of columns of an interleaving matrix used by a stage of the interleaver.

Example 91 may include the method of example 87, wherein the second parameter relates to a column permutation pattern vector of a stage of the interleaver.

Example 92 may include the method of example 91, wherein the column permutation pattern vector is a function of a cell Identifier (ID), a Virtual Cell Identifier (VCID), or a user equipment identifier (UE ID).

Example 93 may include one or more computer-readable media comprising instructions that, when executed by one or more processors of a base station, cause the base station to: sending an indication of a first set of parameters related to Physical Downlink Control Channel (PDCCH) transmissions in a Physical Broadcast Channel (PBCH) transmission; identifying a first parameter related to a Resource Element Group Bundle (REGB) interleaving the PDCCH transmissions, wherein the first parameter is selected from a first plurality of parameters; interleaving the REGB based on the first parameter to form a Control Channel Element (CCE); and transmitting the CCE in the PDCCH transmission according to the first set of parameters related to the PDCCH transmission, wherein the CCE is related to an indication of a second set of parameters related to the PDCCH.

Example 94 may include the one or more computer-readable media of example 93, wherein the indication of the second set of parameters related to the PDCCH is a Remaining Minimum System Information (RMSI) transmission.

Example 95 may include the one or more computer-readable media of example 93, wherein the PBCH transmission is a New Radio (NR) -PBCH transmission.

Example 96 may include the one or more computer-readable media of example 93, wherein the PDCCH transmission is a New Radio (NR) -PDCCH transmission.

Example 97 may include the one or more computer-readable media of example 93, wherein the first set of parameters relates to a first set of timing parameters that may be used by a User Equipment (UE) to monitor for the PDCCH transmission.

Example 98 may include the one or more computer-readable media of example 97, wherein the second set of parameters relates to a second set of timing information usable by a User Equipment (UE) to monitor for a subsequent PDCCH transmission.

Example 99 may include the one or more computer-readable media of example 93, wherein the first set of parameters is a first subset of control channel resource set (CORESET) parameters.

Example 100 may include the one or more computer-readable media of example 99, wherein the second set of parameters is a second subset of CORESET parameters that is different from the first subset of CORESET parameters.

Example 101 may include the one or more computer-readable media of example 93, wherein the REGB is a REGB of a control channel resource set (CORESET) transmission.

Example 102 may include the one or more computer-readable media of any of examples 93-101, wherein the first parameter is related to a number of stages of an interleaver that performs interleaving of the REGB.

Example 103 may include one or more computer-readable media as described in example 102, wherein the instructions are further to: identifying a second parameter related to a REGB of the PDCCH transmission, wherein the second parameter is selected from a second plurality of parameters; and interleaving the REGB based on the second parameter to form the CCE.

Example 104 may include the one or more computer-readable media of example 103, wherein the second parameter relates to a number of REGBs in the CCE for a stage of the interleaver.

Example 105 may include the one or more computer-readable media of example 103, wherein the second parameter is related to a number of rows of an interleaving matrix used by a stage of the interleaver.

Example 106 may include the one or more computer-readable media of example 103, wherein the second parameter is related to a number of columns of an interleaving matrix used by a stage of the interleaver.

Example 107 may include the one or more computer-readable media of example 103, wherein the second parameter relates to a column permutation pattern vector of a stage of the interleaver.

Example 108 may include the one or more computer-readable media of example 107, wherein the column permutation pattern vector is a function of a cell Identifier (ID), a Virtual Cell Identifier (VCID), or a user equipment identifier (UE ID).

Example 109 may include a base station, comprising: means for sending an indication of a first set of parameters related to a Physical Downlink Control Channel (PDCCH) transmission in a Physical Broadcast Channel (PBCH) transmission; means for identifying a first parameter related to a Resource Element Group Bundle (REGB) interleaving the PDCCH transmissions, wherein the first parameter is selected from a first plurality of parameters; means for interleaving the REGB based on the first parameter to form a Control Channel Element (CCE); and means for transmitting the CCE in the PDCCH transmission in accordance with the first set of parameters related to the PDCCH transmission, wherein the CCE is related to an indication of a second set of parameters related to the PDCCH.

Example 110 may include the base station of example 109, wherein the indication of the second set of parameters related to the PDCCH is a Remaining Minimum System Information (RMSI) transmission.

Example 111 may include the base station of example 109, wherein the PBCH transmission is a New Radio (NR) -PBCH transmission.

Example 112 may include the base station of example 109, wherein the PDCCH transmission is a New Radio (NR) -PDCCH transmission.

Example 113 may include the base station of example 109, wherein the first set of parameters relates to a first set of timing parameters that may be used by a User Equipment (UE) to monitor the PDCCH transmission.

Example 114 may include the base station of example 113, wherein the second set of parameters relates to a second set of timing information that may be used by a User Equipment (UE) to monitor for a subsequent PDCCH transmission.

Example 115 may include the base station of example 109, wherein the first set of parameters is a first subset of control channel resource set (CORESET) parameters.

Example 116 may include the base station of example 115, wherein the second set of parameters is a second subset of CORESET parameters different from the first subset of CORESET parameters.

Example 117 may include the base station of example 109, wherein the REGB is a REGB of a control channel resource set (CORESET) transmission.

Example 118 may include the base station of any one of examples 109 and 117, wherein the first parameter relates to a number of stages of an interleaver performing interleaving of the REGB.

Example 119 may include the base station of example 118, further comprising: means for identifying a second parameter related to REGB of the PDCCH transmission, wherein the second parameter is selected from a second plurality of parameters; and means for interleaving the REGB based on the second parameter to form the CCE.

Example 120 may include the base station of example 119, wherein the second parameter relates to a number of REGBs in the CCE for a phase of the interleaver.

Example 121 may include the base station of example 119, wherein the second parameter relates to a number of rows of an interleaving matrix used by a stage of the interleaver.

Example 122 may include the base station of example 119, wherein the second parameter is related to a number of columns of an interleaving matrix used by a stage of the interleaver.

Example 123 may include the base station of example 119, wherein the second parameter relates to a column permutation pattern vector of a stage of the interleaver.

Example 124 may include the base station of example 123, wherein the column permutation pattern vector is a function of a cell Identifier (ID), a Virtual Cell Identifier (VCID), or a user equipment identifier (UE ID).

Example 125 may include a base station, comprising: a processor; and one or more computer-readable media comprising instructions that, when executed by the processor, cause the base station to: sending an indication of a first set of parameters related to Physical Downlink Control Channel (PDCCH) transmissions in a Physical Broadcast Channel (PBCH) transmission; identifying a first parameter related to a Resource Element Group Bundle (REGB) interleaving the PDCCH transmissions, wherein the first parameter is selected from a first plurality of parameters; interleaving the REGB based on the first parameter to form a Control Channel Element (CCE); and transmitting the CCE in the PDCCH transmission according to the first set of parameters related to the PDCCH transmission, wherein the CCE is related to an indication of a second set of parameters related to the PDCCH.

Example 126 may include the base station of example 125, wherein the indication of the second set of parameters related to the PDCCH is a Remaining Minimum System Information (RMSI) transmission.

Example 127 may include the base station of example 125, wherein the PBCH transmission is a New Radio (NR) -PBCH transmission.

Example 128 may include the base station of example 125, wherein the PDCCH transmission is a New Radio (NR) -PDCCH transmission.

Example 129 may include the base station of example 125, wherein the first set of parameters relates to a first set of timing parameters that may be used by a User Equipment (UE) to monitor the PDCCH transmission.

Example 130 may include the base station of example 129, wherein the second set of parameters relates to a second set of timing information usable by a User Equipment (UE) to monitor for a subsequent PDCCH transmission.

Example 131 may include the base station of example 125, wherein the first set of parameters is a first subset of control channel resource set (CORESET) parameters.

Example 132 may include the base station of example 131, wherein the second set of parameters is a second subset of CORESET parameters that is different from the first subset of CORESET parameters.

Example 133 may include the base station of example 125, wherein the REGB is a REGB of a control channel resource set (CORESET) transmission.

Example 134 may include the base station of any one of examples 125 and 133, wherein the first parameter relates to a number of stages of an interleaver performing interleaving of the REGB.

Example 135 may include the base station of example 134, wherein the instructions are further to: identifying a second parameter related to a REGB of the PDCCH transmission, wherein the second parameter is selected from a second plurality of parameters; and interleaving the REGB based on the second parameter to form the CCE.

Example 136 may include the base station of example 135, wherein the second parameter relates to a number of REGBs in the CCE for a phase of the interleaver.

Example 137 may include the base station of example 135, wherein the second parameter is related to a number of rows of an interleaving matrix used by a stage of the interleaver.

Example 138 may include the base station of example 135, wherein the second parameter is related to a number of columns of an interleaving matrix used by a stage of the interleaver.

Example 139 may include the base station of example 135, wherein the second parameter relates to a column permutation pattern vector of a stage of the interleaver.

Example 140 may include the base station of example 139, wherein the column permutation pattern vector is a function of a cell Identifier (ID), a Virtual Cell Identifier (VCID), or a user equipment identifier (UE ID).

Example 141 may include a method, comprising: identifying, by a User Equipment (UE), an indication of a first set of parameters related to a control channel in a received first physical channel transmission; and identifying, by the UE, an indication of a second set of parameters related to the control channel in the received control channel transmission based on the first set of parameters.

Example 142 may include the method of example 141, wherein the first physical channel transmission is a Physical Broadcast Channel (PBCH) transmission.

Example 143 may include the method of example 142, wherein the PBCH transmission is a New Radio (NR) -PBCH transmission.

Example 144 may include the method of example 141, wherein the control channel transmission is a Physical Downlink Control Channel (PDCCH) transmission.

Example 145 may include the method of example 144, wherein the PDCCH transmission is a New Radio (NR) -PDCCH transmission.

Example 146 may include the method of example 144, wherein the control channel transmission relates to a Physical Downlink Shared Channel (PDSCH) transmission including Remaining Minimal System Information (RMSI) elements.

Example 147 may include the method of any of example 141-146, wherein the first set of parameters relates to a first set of timing parameters that may be used by the UE to monitor for the control channel transmission.

Example 148 may include the method of example 147, wherein the second set of parameters relates to a second set of timing information that may be used by the UE to monitor for subsequent control channel transmissions.

Example 149 may include the method of any one of examples 141 and 146, wherein the first set of parameters is a first subset of control channel resource set (CORESET) parameters.

Example 150 may include the method of example 149, wherein the second set of parameters is a second subset of CORESET parameters that is different from the first subset of CORESET parameters.

Example 151 may include one or more computer-readable media comprising instructions that, when executed by one or more processors of a User Equipment (UE), cause the UE to: identifying, in the received first physical channel transmission, an indication of a first set of parameters related to the control channel; and identifying, in a received control channel transmission based on the first set of parameters, an indication of a second set of parameters related to the control channel.

Example 152 may include the one or more computer-readable media of example 151, wherein the first physical channel transmission is a Physical Broadcast Channel (PBCH) transmission.

Example 153 may include the one or more computer-readable media of example 152, wherein the PBCH transmission is a New Radio (NR) -PBCH transmission.

Example 154 may include the one or more computer-readable media of example 151, wherein the control channel transmission is a Physical Downlink Control Channel (PDCCH) transmission.

Example 155 may include the one or more computer-readable media of example 154, wherein the PDCCH transmission is a New Radio (NR) -PDCCH transmission.

Example 156 may include the one or more computer-readable media of example 154, wherein the control channel transmission relates to a Physical Downlink Shared Channel (PDSCH) transmission including Remaining Minimal System Information (RMSI) elements.

Example 157 may include the one or more computer-readable media of any one of examples 151-156, wherein the first set of parameters relates to a first set of timing parameters that may be used by the UE to monitor for the control channel transmission.

Example 158 may include the one or more computer-readable media of example 157, wherein the second set of parameters relates to a second set of timing information usable by the UE to monitor for subsequent control channel transmissions.

Example 159 may include the one or more computer-readable media of any one of examples 151-156, wherein the first set of parameters is a first subset of control channel resource set (CORESET) parameters.

Example 160 may include the one or more computer-readable media of example 159, wherein the second set of parameters is a second subset of CORESET parameters different from the first subset of CORESET parameters.

Example 161 may include a User Equipment (UE), comprising: means for identifying, in the received first physical channel transmission, an indication of a first set of parameters related to a control channel; and means for identifying, in a received control channel transmission based on the first set of parameters, an indication of a second set of parameters related to the control channel.

Example 162 may include the UE of example 161, wherein the first physical channel transmission is a Physical Broadcast Channel (PBCH) transmission.

Example 163 may include the UE of example 162, wherein the PBCH transmission is a New Radio (NR) -PBCH transmission.

Example 164 may include the UE of example 161, wherein the control channel transmission is a Physical Downlink Control Channel (PDCCH) transmission.

Example 165 may include the UE of example 164, wherein the PDCCH transmission is a New Radio (NR) -PDCCH transmission.

Example 166 may include the UE of example 164, wherein the control channel transmission relates to a Physical Downlink Shared Channel (PDSCH) transmission including a Remaining Minimum System Information (RMSI) element.

Example 167 may include the UE of any one of examples 161-166, wherein the first set of parameters relates to a first set of timing parameters that may be used by the UE to monitor the control channel transmission.

Example 168 may include the UE of example 167, wherein the second set of parameters relates to a second set of timing information that may be used by the UE to monitor for a subsequent control channel transmission.

Example 169 may include the UE of any one of examples 161-166, wherein the first set of parameters is a first subset of control channel resource set (CORESET) parameters.

Example 170 may include the UE of example 169, wherein the second set of parameters is a second subset of CORESET parameters different from the first subset of CORESET parameters.

Example 171 may include a User Equipment (UE), comprising: a processor; and one or more computer-readable media comprising instructions that, when executed by the processor, cause the UE to: identifying, in the received first physical channel transmission, an indication of a first set of parameters related to the control channel; and identifying, in a received control channel transmission based on the first set of parameters, an indication of a second set of parameters related to the control channel.

Example 172 may include the UE of example 171, wherein the first physical channel transmission is a Physical Broadcast Channel (PBCH) transmission.

Example 173 may include the UE of example 172, wherein the PBCH transmission is a New Radio (NR) -PBCH transmission.

Example 174 may include the UE of example 171, wherein the control channel transmission is a Physical Downlink Control Channel (PDCCH) transmission.

Example 175 may include the UE of example 174, wherein the PDCCH transmission is a New Radio (NR) -PDCCH transmission.

Example 176 may include the UE of example 174, wherein the control channel transmission relates to a Physical Downlink Shared Channel (PDSCH) transmission including Remaining Minimal System Information (RMSI) elements.

Example 177 may include the UE of any of examples 171-176, wherein the first set of parameters relates to a first set of timing parameters that may be used by the UE to monitor for the control channel transmission.

Example 178 may include the UE of example 177, wherein the second set of parameters relates to a second set of timing information that may be used by the UE to monitor for subsequent control channel transmissions.

Example 179 may include the UE of any one of examples 171-176, wherein the first set of parameters is a first subset of control channel resource set (CORESET) parameters.

Example 180 may include the UE of example 179, wherein the second set of parameters is a second subset of CORESET parameters different from the first subset of CORESET parameters.

Example 181 may include a method, comprising: identifying, by a User Equipment (UE), a Physical Downlink Control Channel (PDCCH) transmission received from a base station; and identifying, by the UE, a Control Channel Element (CCE) in the PDCCH transmission; wherein the CCE is based on interleaving a Resource Element Group Bundle (REGB) of the PDCCH transmission by the base station based on a first parameter selected from a first plurality of parameters related to the REGB.

Example 182 may include the method of example 181, wherein the REGB is a REGB transmitted by a set of control channel resources (CORESET).

Example 183 may include the method of example 181-182, wherein the first parameter relates to a number of stages of an interleaver that performs interleaving of the REGB.

Example 184 may include the method of example 183, wherein the CCE further interleaves, by the base station, the REGB based on a second parameter related to the REGB of the PDCCH transmission.

Example 185 may include the method of example 184, wherein the second parameter relates to a number of REGBs in the CCE for a stage of the interleaver.

Example 186 may include the method of example 184, wherein the second parameter is related to a number of rows of an interleaving matrix used by a stage of the interleaver.

Example 187 may include the method of example 184, wherein the second parameter relates to a number of columns of an interleaving matrix used by a stage of the interleaver.

Example 188 may include the method of example 184, wherein the second parameter relates to a column permutation pattern vector of a stage of the interleaver.

Example 189 may include the method of example 188, wherein the column permutation pattern vector is a function of a cell Identifier (ID), a Virtual Cell Identifier (VCID), or a user equipment identifier (UE ID).

Example 190 may include one or more computer-readable media comprising instructions that, when executed by one or more processors of a User Equipment (UE), cause the UE to: identifying a Physical Downlink Control Channel (PDCCH) transmission received from a base station; and identifying a Control Channel Element (CCE) in the PDCCH transmission; wherein the CCE is based on interleaving a Resource Element Group Bundle (REGB) of the PDCCH transmission by the base station based on a first parameter selected from a first plurality of parameters related to the REGB.

Example 191 may include the one or more computer-readable media of example 190, wherein the REGB is a REGB of a control channel resource set (CORESET) transmission.

Example 192 may include the one or more computer-readable media of examples 190 or 191, wherein the first parameter relates to a number of stages of an interleaver that performs interleaving of the REGB.

Example 193 may include the one or more computer-readable media of example 192, wherein the CCE further interleaves the REGB transmitted by the base station based on a second parameter related to the REGB.

Example 194 may include the one or more computer-readable media of example 193, wherein the second parameter relates to a number of REGBs in the CCE for a stage of the interleaver.

Example 195 may include the one or more computer-readable media of example 193, wherein the second parameter is related to a number of rows of an interleaving matrix used by a stage of the interleaver.

Example 196 may include the one or more computer-readable media of example 193, wherein the second parameter is related to a number of columns of an interleaving matrix used by a stage of the interleaver.

Example 197 may include the one or more computer-readable media of example 193, wherein the second parameter relates to a column permutation pattern vector of a stage of the interleaver.

Example 198 may include the one or more computer-readable media of example 197, wherein the column permutation mode vector is a function of a cell Identifier (ID), a Virtual Cell Identifier (VCID), or a user equipment identifier (UE ID).

Example 199 may include a User Equipment (UE), comprising: means for identifying a Physical Downlink Control Channel (PDCCH) transmission received from a base station; and means for identifying a Control Channel Element (CCE) in the PDCCH transmission; wherein the CCE is based on interleaving a Resource Element Group Bundle (REGB) of the PDCCH transmission by the base station based on a first parameter selected from a first plurality of parameters related to the REGB.

Example 200 may include the UE of example 199, wherein the REGB is a REGB transmitted by a set of control channel resources (CORESET).

Example 201 may include the UE of example 199-200, wherein the first parameter relates to a number of stages of an interleaver that perform interleaving of the REGB.

Example 202 may include the UE of example 201, wherein the CCE further interleaves, by the base station, the REGB based on a second parameter related to the REGB of the PDCCH transmission.

Example 203 may include the UE of example 202, wherein the second parameter relates to a number of REGBs in the CCE for a phase of the interleaver.

Example 204 may include the UE of example 202, wherein the second parameter is related to a number of rows of an interleaving matrix used by a stage of the interleaver.

Example 205 may include the UE of example 202, wherein the second parameter relates to a number of columns of an interleaving matrix used by a stage of the interleaver.

Example 206 may include the UE of example 202, wherein the second parameter relates to a column permutation pattern vector of a stage of the interleaver.

Example 207 may include the UE of example 206, wherein the column permutation pattern vector is a function of a cell Identifier (ID), a Virtual Cell Identifier (VCID), or a user equipment identifier (UE ID).

Example 208 may include a User Equipment (UE), comprising: a processor; and one or more computer-readable media comprising instructions that, when executed by the processor, cause the UE to: identifying a Physical Downlink Control Channel (PDCCH) transmission received from a base station; and identifying a Control Channel Element (CCE) in the PDCCH transmission; wherein the CCE is based on interleaving a Resource Element Group Bundle (REGB) of the PDCCH transmission by the base station based on a first parameter selected from a first plurality of parameters related to the REGB.

Example 209 may include the UE of example 208, wherein the REGB is a REGB of a control channel resource set (CORESET) transmission.

Example 210 may include the UE of example 208 or 209, wherein the first parameter relates to a number of stages of an interleaver that perform interleaving of the REGB.

Example 211 may include the UE of example 210, wherein the CCE further interleaves, by the base station, the REGB based on a second parameter related to the REGB for the PDCCH transmission.

Example 212 may include the UE of example 211, wherein the second parameter relates to a number of REGBs in the CCE for a phase of the interleaver.

Example 213 may include the UE of example 211, wherein the second parameter is related to a number of rows of an interleaving matrix used by a stage of the interleaver.

Example 214 may include the UE of example 211, wherein the second parameter relates to a number of columns of an interleaving matrix used by a stage of the interleaver.

Example 215 may include the UE of example 211, wherein the second parameter relates to a column permutation pattern vector of a stage of the interleaver.

Example 216 may include the UE of example 215, wherein the column permutation pattern vector is a function of a cell Identifier (ID), a Virtual Cell Identifier (VCID), or a user equipment identifier (UE ID).

Example 217 may include a method, comprising: identifying, by a User Equipment (UE), an indication of a first set of parameters related to a Physical Downlink Control Channel (PDCCH) transmission in a Physical Broadcast Channel (PBCH) transmission received from a base station; identifying the PDCCH transmission received from the base station; and identifying, by the UE, a Control Channel Element (CCE) in the PDCCH transmission as a function of the first set of parameters, wherein the CCE is related to an indication of a second set of parameters related to the PDCCH; wherein the CCE is based on interleaving, by the base station, the REGB based on a first parameter to form the CCE; and wherein the first parameter relates to a Resource Element Group Bundle (REGB) interleaving the PDCCH transmissions and is selected by the base station from a first plurality of parameters.

Example 218 may include the method of example 217, wherein the indication of the second set of parameters related to the PDCCH is a Remaining Minimum System Information (RMSI) transmission.

Example 219 may include the method of example 217, wherein the PBCH transmission is a New Radio (NR) -PBCH transmission.

Example 220 may include the method of example 217, wherein the PDCCH transmission is a New Radio (NR) -PDCCH transmission.

Example 221 may include the method of example 217, wherein the first set of parameters relates to a first set of timing parameters that may be used by the UE to monitor for the PDCCH transmission.

Example 222 may include the method of example 221, wherein the second set of parameters relates to a second set of timing information that may be used by the UE to monitor for subsequent PDCCH transmissions.

Example 223 may include the method of example 217, wherein the first set of parameters is a first subset of control channel resource set (CORESET) parameters.

Example 224 may include the method of example 223, wherein the second set of parameters is a second subset of CORESET parameters that is different from the first subset of CORESET parameters.

Example 225 may include the method of example 217, wherein the REGB is a REGB transmitted by a set of control channel resources (CORESET).

Example 226 may include the method of any of examples 217 and 225, wherein the first parameter relates to a number of stages of an interleaver that performs interleaving of the REGB.

Example 227 may include the method of example 226, wherein the CCE is further based on interleaving the REGB by the base station based on a second parameter selected from a second plurality of parameters to form the CCE.

Example 228 may include the method of example 227, wherein the second parameter relates to a number of REGBs in the CCE for a stage of the interleaver.

Example 229 may include the method of example 227, wherein the second parameter relates to a number of rows of an interleaving matrix used by a stage of the interleaver.

Example 230 may include the method of example 227, wherein the second parameter is related to a number of columns of an interleaving matrix used by a stage of the interleaver.

Example 231 may include the method of example 227, wherein the second parameter relates to a column permutation pattern vector of a stage of the interleaver.

Example 232 may include the method of example 231, wherein the column permutation pattern vector is a function of a cell Identifier (ID), a Virtual Cell Identifier (VCID), or a UE ID.

Example 233 may include one or more computer-readable media comprising instructions that, when executed by one or more processors of a User Equipment (UE), cause the UE to: identifying, in a Physical Broadcast Channel (PBCH) transmission received from a base station, an indication of a first set of parameters related to a Physical Downlink Control Channel (PDCCH) transmission; identifying the PDCCH transmission received from the base station; and identifying, by the UE, a Control Channel Element (CCE) in the PDCCH transmission as a function of the first set of parameters, wherein the CCE is related to an indication of a second set of parameters related to the PDCCH; wherein the CCE is based on interleaving, by the base station, the REGB based on a first parameter to form the CCE; and wherein the first parameter relates to a Resource Element Group Bundle (REGB) interleaving the PDCCH transmissions and is selected by the base station from a first plurality of parameters.

Example 234 may include the one or more computer-readable media of example 233, wherein the indication of the second set of parameters related to the PDCCH is a Remaining Minimum System Information (RMSI) transmission.

Example 235 may include the one or more computer-readable media of example 233, wherein the PBCH transmission is a New Radio (NR) -PBCH transmission.

Example 236 may include the one or more computer-readable media of example 233, wherein the PDCCH transmission is a New Radio (NR) -PDCCH transmission.

Example 237 may include the one or more computer-readable media of example 233, wherein the first set of parameters relates to a first set of timing parameters that may be used by the UE to monitor for the PDCCH transmission.

Example 238 may include the one or more computer-readable media of example 237, wherein the second set of parameters relates to a second set of timing information usable by the UE to monitor for a subsequent PDCCH transmission.

Example 239 may include the one or more computer-readable media of example 233, wherein the first set of parameters is a first subset of control channel resource set (CORESET) parameters.

Example 240 may include the one or more computer-readable media of example 239, wherein the second set of parameters is a second subset of CORESET parameters that is different from the first subset of CORESET parameters.

Example 241 may include the one or more computer-readable media of example 233, wherein the REGB is a REGB of a control channel resource set (CORESET) transmission.

Example 242 may include the one or more computer-readable media of any of examples 233-241, wherein the first parameter relates to a number of stages of an interleaver that performs interleaving of the REGB.

Example 243 may include the one or more computer-readable media of example 242, wherein the CCE is further based on interleaving, by the base station, the REGB based on a second parameter selected from a second plurality of parameters to form the CCE.

Example 244 may include the one or more computer-readable media of example 243, wherein the second parameter relates to a number of REGBs in the CCE for a stage of the interleaver.

Example 245 may include the one or more computer-readable media of example 243, wherein the second parameter is related to a number of rows of an interleaving matrix used by a stage of the interleaver.

Example 246 may include the one or more computer-readable media of example 243, wherein the second parameter relates to a number of columns of an interleaving matrix used by a stage of the interleaver.

Example 247 may include the one or more computer-readable media of example 243, wherein the second parameter relates to a column permutation pattern vector of a stage of the interleaver.

Example 248 may include the one or more computer-readable media of example 247, wherein the column permutation mode vector is a function of a cell Identifier (ID), a Virtual Cell Identifier (VCID), or a UE ID.

Example 249 may include a User Equipment (UE), comprising: means for identifying, in a Physical Broadcast Channel (PBCH) transmission received from a base station, an indication of a first set of parameters related to a Physical Downlink Control Channel (PDCCH) transmission; means for identifying the PDCCH transmission received from the base station; and means for identifying, by the UE, a Control Channel Element (CCE) in the PDCCH transmission in accordance with the first set of parameters, wherein the CCE is related to an indication of a second set of parameters related to the PDCCH; wherein the CCE is based on interleaving, by the base station, the REGB based on a first parameter to form the CCE; and wherein the first parameter relates to a Resource Element Group Bundle (REGB) interleaving the PDCCH transmissions and is selected by the base station from a first plurality of parameters.

Example 250 may include the UE of example 249, wherein the indication of the second set of parameters related to the PDCCH is a Remaining Minimum System Information (RMSI) transmission.

Example 251 may include the UE of example 249, wherein the PBCH transmission is a New Radio (NR) -PBCH transmission.

Example 252 may include the UE of example 249, wherein the PDCCH transmission is a New Radio (NR) -PDCCH transmission.

Example 253 may include the UE of example 249, wherein the first set of parameters relates to a first set of timing parameters that may be used by the UE to monitor for the PDCCH transmission.

Example 254 may include the UE of example 253, wherein the second set of parameters relates to a second set of timing information that may be used by the UE to monitor for a subsequent PDCCH transmission.

Example 255 may include the UE of example 249, wherein the first set of parameters is a first subset of control channel resource set (CORESET) parameters.

Example 256 may include the UE of example 255, wherein the second set of parameters is a second subset of CORESET parameters different from the first subset of CORESET parameters.

Example 257 may include the UE of example 249, wherein the REGB is a REGB for control channel resource set (CORESET) transmission.

Example 258 may include the UE of any of examples 249-257, wherein the first parameter relates to a number of stages of an interleaver that performs interleaving of the REGB.

Example 259 may include the UE of example 258, wherein the CCE is further based on interleaving, by the base station, the REGB based on a second parameter to form the CCE, the second parameter selected from a second plurality of parameters.

Example 260 may include the UE of example 259, wherein the second parameter relates to a number of REGBs in the CCE for a stage of the interleaver.

Example 261 may include the UE of example 259, wherein the second parameter relates to a number of rows of an interleaving matrix used by a stage of the interleaver.

Example 262 may include the UE of example 259, wherein the second parameter relates to a number of columns of an interleaving matrix used by a stage of the interleaver.

Example 263 may include the UE of example 259, wherein the second parameter relates to a column permutation pattern vector of a stage of the interleaver.

Example 264 may include the UE of example 263, wherein the column permutation pattern vector is a function of a cell Identifier (ID), a Virtual Cell Identifier (VCID), or a UE ID.

Example 265 may include a User Equipment (UE), comprising: a processor; and one or more computer-readable media comprising instructions that, when executed by the processor, cause the UE to: identifying, in a Physical Broadcast Channel (PBCH) transmission received from a base station, an indication of a first set of parameters related to a Physical Downlink Control Channel (PDCCH) transmission; identifying the PDCCH transmission received from the base station; and identifying, by the UE, a Control Channel Element (CCE) in the PDCCH transmission as a function of the first set of parameters, wherein the CCE is related to an indication of a second set of parameters related to the PDCCH; wherein the CCE is based on interleaving, by the base station, the REGB based on a first parameter to form the CCE; and wherein the first parameter relates to a Resource Element Group Bundle (REGB) interleaving the PDCCH transmissions and is selected by the base station from a first plurality of parameters.

Example 266 may include the UE of example 265, wherein the indication of the second set of parameters related to the PDCCH is a Remaining Minimum System Information (RMSI) transmission.

Example 267 may include the UE of example 265, wherein the PBCH transmission is a New Radio (NR) -PBCH transmission.

Example 268 may include the UE of example 265, wherein the PDCCH transmission is a New Radio (NR) -PDCCH transmission.

Example 269 may include the UE of example 265, wherein the first set of parameters relates to a first set of timing parameters that may be used by the UE to monitor for the PDCCH transmission.

Example 270 may include the UE of example 269, wherein the second set of parameters relates to a second set of timing information that may be used by the UE to monitor for a subsequent PDCCH transmission.

Example 271 may include the UE of example 265, wherein the first set of parameters is a first subset of control channel resource set (CORESET) parameters.

Example 272 may include the UE of example 271, wherein the second set of parameters is a second subset of CORESET parameters different from the first subset of CORESET parameters.

Example 273 may include the UE of example 265, wherein the REGB is a REGB of a control channel resource set (CORESET) transmission.

Example 274 may include the UE of any of examples 265-273, wherein the first parameter relates to a number of stages of an interleaver that performs interleaving of the REGB.

Example 275 may include the UE of example 274, wherein the CCE is further based on interleaving the REGB by the base station based on a second parameter selected from a second plurality of parameters to form the CCE.

Example 276 may include the UE of example 275, wherein the second parameter relates to a number of REGBs in the CCE for a stage of the interleaver.

Example 277 may include the UE of example 275, wherein the second parameter is related to a number of rows of an interleaving matrix used by a stage of the interleaver.

Example 278 may include the UE of example 275, wherein the second parameter relates to a number of columns of an interleaving matrix used by the stage of the interleaver.

Example 279 may include the UE of example 275, wherein the second parameter relates to a column permutation pattern vector of a stage of the interleaver.

Example 280 may include the UE of example 279, wherein the column permutation pattern vector is a function of a cell Identifier (ID), a Virtual Cell Identifier (VCID), or a UE ID.

Example 281 may include a fully configurable interleaver, consisting of one or several sequential interleaving stages. The number of interleaving stages N _ I is configurable.

Example 282 may include the subject matter as described in example 281 or some other example herein, wherein each configurable interleaving stage may involve three steps.

Example 283 may include writing the configurable rectangular interleaving matrix row by row in column ascending order in step 1.

Example 284 may include performing a configurable column permutation operation on the padded interleaving matrix in step 2.

Example 285 may include reading the interleaving matrix column by column in ascending row order in step 3.

Example 286 may include that the following parameters may be configured in the nth interleaving stage, where N1.. N _ I:

o interleaving unit in terms of number of REGBs: b _ n

Number of rows of the o-interlace matrix: r _ n

Number of columns of the o-interleaving matrix: c n

o column permutation function: f n (c), where c is 1, 2.

Example 287 may include that some of the configurable parameters may be a function of other parameters.

Example 288 may include a network configurable CORESET of X REGBs and each CCE contains Y REGBs. The interleaver may be configured with the following settings:

o N I＝1

o B＝1

o R＝Y

o C＝X/Y

o c _ p may be any deterministic function of cell or virtual ID and/or UE ID or other parameters.

Example 289 may include the CCE obtained from example 8 being fully distributed over CORESET.

Example 290 may include that CCEs with consecutive indices may also be evenly distributed over CORESET, such that high aggregation level PDCCHs comprising several consecutive CCEs in the hierarchical search space are also evenly distributed over the entire CORESET.

Example 291 may include that the interleaver may also be configured with the following settings:

o N I＝1

o B＝1

o R may be greater than Y

o C＝X/R

Example 292 may include that the span of CCEs generated from example 291 is only in a portion of the CORESET, and more CCEs with consecutive indices may be distributed throughout the CORESET.

Example 293 may include that the interleaver may also be configured with the following settings:

o N I＝1

o B＝1

o R may be less than Y

o C＝X/R

Example 294 may include the span of CCEs resulting from example 293 in several segments of consecutive REGBs. This further reduced distributed CCE allocation may be able to reduce the blocking probability of multiple overlapping CORESET configurations.

In example 295, the network can select a preferred interleaving setting according to desired design goals and system control resource configurations.

Example 296 may include a method of wireless communication for a fifth generation (5G) or New Radio (NR) system, the method comprising: the UE is configured with a set of control resources for monitoring the control channel.

Example 297 may include a method as described in example 296 and/or some other example herein, wherein the set of control resources is configured with two steps.

Example 298 may include the method of example 297 and/or some other example herein, wherein the first step is performed by a broadcast channel and comprises a portion of the overall configuration information.

Example 299 may include the method of example 297 and/or some other example herein, wherein the second step is accomplished by a control data channel and comprises all or a portion of the overall configuration information.

Example 300 may include the method of example 298 and/or some other example herein, wherein the configuration by the first step should be sufficient to enable the UE to receive a control channel with a configured CORESET before the second step is completed.

Example 301 may include the method of example 300 and/or some other example herein, wherein the CORESET configuration parameters that were not configured in the first step have a default mode that the UE assumed for reception of control channels in CORESET before the second step.

Example 302 may include a method of wireless communication for a fifth generation (5G) or New Radio (NR) system, the method comprising: the parameter set of the CORESET is configured for the random access procedure.

Example 303 may include the method of example 302 and/or some other example herein, wherein the set of control resources is configured with more than two steps and each step is to include all or some of the CORESET configuration information.

Example 304 may include the method of example 303 and/or some other example herein, wherein the set of parameters for the CORESET is mapped to a set of parameters for a random access channel configured by the broadcast channel.

Example 305 may include some combination of one or more of the above examples.

Example 306 may include an apparatus comprising means for performing one or more elements of a method described in or relating to any of examples 1-305, or any other method or process described herein.

Example 307 may include one or more computer-readable media comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in any of examples 1-305 or in connection with any of examples 1-305, or any other method or process described herein.

Example 308 may include an apparatus comprising logic, a module, or circuitry to perform one or more elements of a method described in or relating to any of examples 1-16, or any other method or process described herein.

Example 309 may include a method, technique, or process as described in any of examples 1-16 or in relation to any of examples 1-16, or some portion thereof.

Example 310 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions, which when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process as described in any of examples 1-16 or in relation to any of examples 1-16, or some portion thereof.

Example 311 may include a signal as described in any of examples 1-16 or in relation to any of examples 1-16, or some portion thereof.

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

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

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

Example 315 may include an apparatus for providing wireless communications as shown and described herein.

Various embodiments may include any suitable combination of the above-described embodiments, including alternative (or) embodiments (e.g., "and" may be "and/or") to those described above in conjunction (and) some embodiments may include one or more articles of manufacture (e.g., a non-transitory computer-readable medium) having stored thereon instructions that, when executed, result in the actions of any of the above-described embodiments. Additionally, some embodiments may include devices or systems having any suitable means for performing the various operations of the embodiments described above.

The above description of illustrated implementations of the invention, including those described in the abstract, is not intended to be exhaustive or to limit the invention to the precise forms disclosed. While specific implementations of, and examples for, the invention are described herein for illustrative purposes, various equivalent modifications are possible within the scope of the invention, as those skilled in the relevant art will recognize. These modifications can be made to the invention in light of the above detailed description. The terms used in the following claims should not be construed to limit the invention to the specific implementations disclosed in the specification and the claims. Rather, the scope of the invention is to be determined entirely by the following claims, which are to be construed in accordance with established doctrines of claim interpretation.

Claims

1. A base station, comprising:

a processor; and

one or more computer-readable media communicatively coupled with the processor, wherein the one or more computer-readable media comprise instructions that, when executed by the processor, cause the processor to:

transmitting an indication of a first set of parameters related to a control channel in a first physical channel transmission; and is

Transmitting, in a control channel transmission, an indication of a second set of parameters related to the control channel using the first set of parameters.

2. The base station of claim 1, wherein the first physical channel transmission is a Physical Broadcast Channel (PBCH) transmission.

3. The base station of claim 1, wherein the control channel transmission is a Physical Downlink Control Channel (PDCCH) transmission.

4. The base station of claim 3, wherein the control channel transmission relates to a Physical Downlink Shared Channel (PDSCH) transmission, the PDSCH transmission including Remaining Minimal System Information (RMSI) elements.

5. The base station of any of claims 1-4, wherein the first set of parameters relates to a first set of timing parameters that can be used by a User Equipment (UE) to monitor the control channel transmission.

6. The base station of claim 5, wherein the second set of parameters relates to a second set of timing information usable by a User Equipment (UE) to monitor for subsequent control channel transmissions.

7. The base station of any of claims 1-4, wherein the first set of parameters is a first subset of control channel resource set (CORESET) parameters.

8. The base station of claim 7, wherein the second set of parameters is a second subset of CORESET parameters different from the first subset of CORESET parameters.

9. A method, comprising:

identifying, by a base station, a first parameter related to a Resource Element Group Bundle (REGB) of an interleaved Physical Downlink Control Channel (PDCCH) transmission, wherein the first parameter is selected from a first plurality of parameters;

interleaving, by the base station, the REGB based on the first parameter to form a Control Channel Element (CCE); and is

Transmitting, by the base station, the CCE in the PDCCH transmission.

10. The method of claim 9, wherein the REGB is a REGB transmitted by a control channel resource set (CORESET).

11. The method of claim 9 or 10, wherein the first parameter is related to a number of stages of an interleaver that performs interleaving of the REGB.

12. The method of claim 11, further comprising:

identifying, by the base station, a second parameter related to REGB of the PDCCH transmission, wherein the second parameter is selected from a second plurality of parameters; and is

Interleaving, by the base station, the REGB based on the second parameter to form the CCE.

13. The method of claim 12, wherein the second parameter relates to: a number of REGB's in the CCE for a stage of the interleaver, a number of rows of an interleaving matrix used by a stage of the interleaver, a number of columns of an interleaving matrix used by a stage of the interleaver, or a column permutation pattern vector for a stage of the interleaver.

14. One or more computer-readable media comprising instructions that, when executed by one or more processors of a base station, cause the base station to:

sending an indication of a first set of parameters related to Physical Downlink Control Channel (PDCCH) transmissions in a Physical Broadcast Channel (PBCH) transmission;

identifying a first parameter related to a Resource Element Group Bundle (REGB) interleaving the PDCCH transmissions, wherein the first parameter is selected from a first plurality of parameters;

interleaving the REGB based on the first parameter to form a Control Channel Element (CCE); and is

Transmitting the CCE in the PDCCH transmission according to the first set of parameters related to the PDCCH transmission, wherein the CCE is related to an indication of a second set of parameters related to the PDCCH.

15. The one or more computer-readable media of claim 14, wherein the indication of the second set of parameters related to the PDCCH is a Remaining Minimal System Information (RMSI) transmission.

16. The one or more computer-readable media of claim 14, wherein the PBCH transmission is a New Radio (NR) -PBCH transmission.

17. The one or more computer-readable media of claim 14, wherein the PDCCH transmission is a New Radio (NR) -PDCCH transmission.

18. The one or more computer-readable media of claim 14, wherein the first set of parameters relates to a first set of timing parameters that are usable by a User Equipment (UE) to monitor the PDCCH transmission.

19. The one or more computer-readable media of claim 18, wherein the second set of parameters relates to a second set of timing information usable by a User Equipment (UE) to monitor for subsequent PDCCH transmissions.

20. The one or more computer-readable media of claim 14, wherein the first set of parameters is a first subset of control channel resource set (CORESET) parameters.

21. The one or more computer-readable mediums of claim 20, wherein the second set of parameters is a second subset of CORESET parameters that is different from the first subset of CORESET parameters.

22. The one or more computer-readable media of claim 14, wherein the REGB is a REGB transmitted by a set of control channel resources (CORESET).

23. The one or more computer-readable media of any of claims 14-22, wherein the first parameter relates to a number of stages of an interleaver that perform interleaving of the REGB.

24. One or more computer-readable media as recited by claim 23, wherein the instructions further:

identifying a second parameter related to a REGB of the PDCCH transmission, wherein the second parameter is selected from a second plurality of parameters; and is

Interleaving the REGB based on the second parameter to form the CCE.

25. One or more computer-readable media as recited by claim 24, wherein the second parameter relates to: a number of REGB's in the CCE for a stage of the interleaver, a number of rows of an interleaving matrix used by a stage of the interleaver, a number of columns of an interleaving matrix used by a stage of the interleaver, or a column permutation pattern vector for a stage of the interleaver.